Hands-On Microservices with Kubernetes

The uniformity versus flexibility trade-off

Let's say you have a hundred microservices, but they are all very small and very similar. They all use the same data store (for example, the same type of relational database). They are all configured in the same way (for example, a configuration file). They all report errors and logs to a centralized log server. They are all implemented using the same programming language (for example, Go). Typically, the system will handle several use cases. Each use case will involve some subset of these hundred microservices. There will also be some generic microservices that are used in most use cases (for example, an authorization service). Then, it may not be that difficult to understand the system as a whole, ...