With all this hype around Kubernetes, containerization and microservices architecture... you cannot help but wonder: “what are the primary Kubernetes use cases, more precisely?” “And is it a good fit for large-scale applications?” Say you have this complex setup: an eCommerce app carrying an ecosystem of about 6 micro-services. You'd expect 2 of them, let's say, to be for internal use-only and 4 of them to have external load balancers... How would Kubernetes orchestrate such a large cluster? What makes it a top choice for automating the deployment of such complex and dynamic infrastructures?

Sharding, loose coupling, scalability... and these are just some of the clear advantages. It's a fact: microservices-styled, container-based architecture is the (not so) new way of building modern applications! One contrasting the traditional “monolithic” approach to app development. And so, adopting the very best practices for building microservices becomes crucial for you, the microservices-based app developer, right? And this is precisely what I'll do my best to achieve with this post: to reveal to you the 2018 standards to adhere to and the...