The microservices pattern breaks down the problem statement into smaller components, which have well-defined boundaries. By breaking down the problem into smaller parts, it is easy to handle and there is a better chance of targeting the solution as it is required. Until now, we have seen that all these advantages that come with some trade-offs. These trade-offs come with another set of problems. From scaling to monitoring, everything is multiplied. If you feel monitoring a monolithic architecture was hard, it's 10 times harder with microservices and requires a bigger investment in planning ahead.
In this section, we will understand some of the common issues normally faced by teams while adopting a microservice.