Microservices with Kubernetes

Chapter 1 discussed various levels of service granularity. As you keep splitting services into finer services, you are in fact increasing the number of moving parts in your architecture. This kind of divide-and-conquer approach in splitting to finer services is attempting to decrease the risk of an individual service failure bringing down your entire application. But on the other hand, as you increase the number of moving parts, you also increase the number of links between these moving parts, thus increasing the blast area prone to failures. We need a toolset and an ecosystem to better manage our microservices application when the complexity increases, and this is where we need to look at Kubernetes which is covered in this chapter.