it-eXperts IT-Dienstleistungs GmbH’s Post

As busy developers we have no time to fix flaky tests! Avoid them by using Awaitility! Learn how to use it in our first blog post 🙂

What are golden paths? 🛤 As #CNCF defines Golden Path is a "templated composition of well-integrated code and capabilities for rapid project development." Golden or paved paths within platforms are predefined routes that outline the best practices, steps, and tools needed to achieve a specific goal. These structured pathways guide developers through building, deploying, and testing applications effectively. For instance, consider the process of building and deploying a web application. A golden path for this use case includes a development environment with node.js, configuring docker containers, Git for version control, Jenkins for CI/CD, Kubernetes for container orchestration, and MongoDB for data management. Automation streamlines tasks like building, testing, and deployment. This guided workflow or template of a golden path equips new developers with the necessary tools and configurations to kickstart the development process efficiently. Golden Paths should be based on the below golden principles: - Single path for one process - It should reduce the load - Customisation thresholds should be available - Adhere to self-service #GoldenPaths #SoftwareDevelopment #BestPractices #Automation #platformengineering

5 Key practices of #ContractDrivenDevelopment explained! Let me know how this matches with your experience?

Integration tests are so much better with TestContainers! Gone are the days of complex setups for external dependencies. With TestContainers, we get lightweight, disposable instances of databases, message brokers, and more, all in Docker containers. This means: 📈 Improved test reliability and production-like environments 🔄 Seamless CI/CD integration 🛠️ No more “it works on my machine” issues TestContainers make our integration tests not just better, but efficient and consistent. A true game-changer for developers! 🌟 #DevOps #Testing #SoftwareDevelopment #TestContainers

Contract-Driven Development (CDD) is a vital component of developing and deploying #microservices independently. Here are 5 key practices of #CDD: 1. API design first: Collaboratively design and document the API using standard specifications. 2. Central Git Repo: Treat the API specs as code and store it in a central Git repository. Let this central Git repo be the single-source of truth referenced by both providers and consumers. 3. Spec Quality Control: Perform compatibility checks to ensure we are not accidentally breaking backward compatibility. Also performing #linting to ensure the #APIDesign meets the agreed-upon specification standards. 4. Automated #ContractTesting: Convert API specifications like #OpenAPI, #AsyncAPI or #WSDL into executable contracts without writing any code. Run these tests in the CI/CD pipeline to shift-left and detect integration issues early. 5. Intelligent Service Virtualisation: Use the contract as a stub. When expectations are set against this stub, they are validated against the contract to ensure the consumers and providers don't drift away. Learn more about #ContractDrivenDevelopment:  https://confng.in/NqVR0Jbf #APItesting #cicdpipelines #Specmatic Naresh Jain, Dave Farley, OpenAPI Initiative, AsyncAPI Initiative

We are thrilled to announce the release of #TungstenCluster & #TungstenReplicator v7.1.3! This update brings a host of new features, including command enhancements, Ruby 3.2 support, and improved tools for enhanced usability and stability. Additionally, several bug fixes address issues with command-line tools and monitoring. We encourage all users to upgrade to v7.1.3 and take advantage of these improvements. For more details, read the following blog post: https://lnkd.in/d6yHYaxK #TechUpdate #DevOps #DatabaseManagement

Dynatrace recently announced 🍾 it has signed a definitive agreement to acquire Rookout, a company that enables developers to quickly troubleshoot and debug actively running code in Kubernetes-hosted cloud-native applications. Adding Rookout to the Dynatrace platform will help developers accelerate innovation and deliver flawless and secure releases. Rookout is a comprehensive debugging platform that supports live debugging across various tech stacks, programming languages (Java, .Net, Node.js, Python, Ruby, Golang, and more), and environments (production, staging, or development). It is suitable for diverse architectures, including on-premises, cloud-native, virtual machines, containers, and serverless setups. The platform enables developers to address any type of issue, including errors, bugs, lags, or mysterious problems. https://lnkd.in/dJrpD4FG #dynatrace #rookout #java #dotnet #nodejs #python #onpremise #cloudnative #virtualmachines #containers #debugging

Understanding #Kubernetes API schema 101 ☸️💡 ➡ Resource Type = API endpoint ➡ Resource Instances = objects served by an endpoint ➡ Resource = an endpoint or an instance, depends on the context ➡ Kind = a schema every resource conforms to ➡ Objects = resource instances acting as records of intent #k8s API is a HTTP API with JSON as its primary serialization schema, however it also supports Protocol Buffers, mainly for cluster-internal communication. For extensibility reasons Kubernetes supports multiple API versions at different API paths, such as '/api/v1' or '/apis/extensions/v1beta1' Different API versions imply different levels of stability and support: 💡 Alpha level, for example v1alpha1 is disabled by default, support for a feature may be dropped at any time without notice and should only be used in short-lived testing clusters. 💡Beta level, for example v2beta3, is enabled by default, means that the code is well tested but the semantics of objects may change in incompatible ways in a subsequent beta or stable release. 💡Stable level, for example, v1 will appear in released software for many subsequent versions. Primitives like #pods, #services, #endpoints, #deployment, etc. make up the objects of the Kubernetes type universe ✅ Kind is the type of an entity. Each object has a field Kind which tells a client—such as kubectl ✅ API Group is a collection of Kinds that are logically related. For example, all batch objects like Job or ScheduledJob are in the batch API Group. ✅ Version. Each API Group can exist in multiple versions. For example, a group first appears as v1alpha1 and is then promoted to v1beta1 and finally graduates to v1 ✅ Resource is the representation of a system entity sent or retrieved as JSON via HTTP; can be exposed as an individual resource (such as .../namespaces/default) or collections of resources (like .../jobs) The #k8s API lives in k8s.io/pkg/api and handles requests from within the cluster as well as to clients outside of the cluster !! Image Credit & Reference - Ivan Velichko #api #developer #devops #deepdive #cloudnative #development #devops #sysops #sre #devopslead #solutionsarchitect #sysadmin #opensource

Read this blog to learn more how “BMC AMI DevX Code Insights is empowering multiple developers to work concurrently, break apart programs, and usher in a new era of agility.”