Operations | Monitoring | ITSM | DevOps | Cloud

Docker is a PaaS product, developed by Docker.Inc to containerize applications. It does so by combining app source code with OS libraries and dependencies required to run that code in any environment. Kubernetes is a similar tool developed by Google, which scales up this containerized application after deployment. While one works in building the containers the other essentially helps in scaling it up, then why so much buzz around these two?

Kubernetes is the de facto leader of container orchestration tools. With the growing popularity of micro-service-based development, Kubernetes emerged as the go-to tool to deploy and manage large-scale enterprise applications. However, with the plethora of features offered by Kubernetes, it is a complex tool to manage and operate. This article will focus on how to configure Kubernetes Audit Logs so that you can have the records of events happening in your cluster.

Data is becoming increasingly essential to businesses globally, allowing for insights to be gathered around critical processes and operations. Over time, the traditional systems put in place to hold our data have become unsuitable for modern-day needs due to the continuous growth of data. Edge computing has emerged to reshape the current computing environment and allow data to be processed closer to where it’s being generated.

Properly testing a service’s APIs to ensure that it can handle production traffic presents many challenges for engineers—SREs need to guarantee the resiliency of their application, while developers must ensure that their features perform well at any given scale. Speedscale is a testing framework built for Kubernetes applications that enables you to load test with real-world production scenarios by replaying actual API traffic that your application has experienced.

Many of the benefits of running Kubernetes come from the efficiencies that you get when you share the cluster – and thus the underlying compute and network resources it manages – between multiple services and teams within your organization. Each of these major services or teams that share the cluster are tenants of the cluster – and thus this approach is referred to as multi-tenancy.

The trend of Platform Engineering is now gaining momentum, which analysts and industry experts refer to as one of the most disruptive philosophies of the moment. But regardless of experts’ predictions and assumptions, what matters for organizations today is understanding what adopting an approach such as Platform Engineering actually entails, what a successful solution looks like, and how to adopt best practices for its implementation. That's what this article is about.