Architectural anti-patterns when delivering a software ecosystem with Kubernetes

The link between architecture and how to deploy a software environment is one of the most important factors to creating a highly available, fast, accessible, reliable, and easy-to-change software service. Laurentiu Spilca explores considerations and common pitfalls when delivering your software with Kubernetes.

There are several factors to take into consideration when working on a software solution: which languages to use, the process, how to deliver, and how all of these have to match with the general architecture. Laurentiu Spilca discusses the links between a clean architecture and the development in an environment orchestrated with Kubernetes. Along the way, Laurentiu explores and proves several anti-patterns and good practices, using hands-on examples. You’ll start by installing Minikube and kubectl and digging into the major resources of a Kubernetes project: deployments, services, pods, and routes. You’ll learn how to integrate them and how to configure load balancing, scaling, and service access. Then, based on the observations you make, you’ll examine several example architecture implementations, try them where possible, and classify them as anti-patterns or good approaches.