In this chapter, we've had a look at what a microservice is and how we can create one. We've discussed how we can separate services using a technique such as a queue, meaning that one microservice is not dependent on another. In using Kubernetes to orchestrate our service, we've seen how this can be a self-healing system.
Along the way, we've looked at Docker and building a Docker image; we've explored container registries and how you can store your Docker images in them; and we've also created and configured an AKS cluster. We've explored the use of both Service Bus and storage queues in Azure, and how they might be used in a distributed system.
As I mentioned in the introduction, this is a very seductive architectural pattern; however, we also discussed how it is not without cost, and that cost is complexity. In replacing a single piece...