Ning Ge and Keith Miracle co-wrote this post. Amidst many social and economic disruptions that have arisen in the last few years, enterprises have been forced to quicken the pace of their digital transformation initiatives, adding and consuming cloud-based capacity and capability just to stay competitive, relevant, and, for some, in business.

Life before containerization was a sore spot for developers. The satisfaction of writing code was constantly overshadowed by the frustration of attempting to force code into production. For many, deployments meant hours of reconfiguring libraries and dependencies for each environment. It was a tedious process prone to error, and it led to a lot of rework. Today, developers can deploy code using new technology such as cloud computing, containers, and container orchestration.

With the 1.2.0 release of Rancher Desktop, there are two new features available as a Feature Preview. Rancher, the multi-cluster Kubernetes manager, includes a dashboard which enables you see and interact with resources in a Kubernetes cluster. Rancher Desktop now includes this dashboard. The dashboard will enable you to view and interact with resources in your local cluster provided by Rancher Desktop.

When I was making my first switch from a product engineering team to being field facing software engineer, one of my first projects was an integration project for a federal agency. The very first piece of enterprise software minus my productivity and development suite I was exposed to was BMC’s Control-M about 15 years ago. A lot of batch files to extract and transform data had to be run in order and on a daily basis; Control-M at the time was a job runner.

Two of the most important questions that people ask themselves on day 2 after adopting GitOps are: In the previous article of the series, I focused on what NOT to do and explained why using Git branches for different environments is a bad idea. I also hinted that the “environment-per-folder” approach is a better idea. This article has proved hugely popular and several people wanted to see all the details about the suggested structure for environments when folders are used.

Welcome to the second post in a series of “How to Scale your AWS Infrastructure”. In the first post, we talked about horizontal scaling, autoscaling, CI/CD, infrastructure automation, containerization, etc. In this post, we will continue the discussion around databases, loose coupling, caching, CDN, etc. Let’s start the discussion with database scaling.