A lot is written about best practices around DevOps and the following guide will highlight some practices that will further enhance your development team’s productivity and happiness.

Programmable data planes offer dynamic control for cloud native applications. Technologies like eBPF and Kubernetes provide an abstraction to improve flexibility, scalability, and performance.

A crucial part of Kubernetes monitoring is about choosing the right tool and methodology. This post introduces 5 popular options.

Our next-generation API management platform built on a Kubernetes-native architecture on top of Envoy Proxy

As more organizations are moving to a cloud-native architecture, there is an ever-increasing need to monitor applications and services. Logging is a crucial part of this process, as it provides the insights and visibility to identify potential issues and track application performance. When it comes to managing and monitoring applications, Docker logging is an essential part of the process.

A Kubernetes preview environment is an isolated environment that allows developers to test their code at any time without worrying about how others may be affected. While implementations and use cases may vary, simulating a production environment as closely as possible is the main goal. Imagine you’re part of a team developing a complex API, and you’ve been tasked with adding a new endpoint that relies on features within the codebase currently being optimized by one of your team members.

A mock server can prove useful in many circumstances. Imagine you’re an engineer working on optimizing a feature inside of an existing API that relies on multiple other microservices to function properly. To fully test the optimizations, you’ll have to set up test versions of all the dependencies, which quickly proves to be quite a task in and of itself. This is where a mocks—a server that simulates the behavior of a real server—can be very beneficial.

In this third and final part, you’ll get to see a few examples that aren’t strictly related to configuration changes or new tools, but rather ways that traffic replay can help streamline the development process for those deploying in Kubernetes.