There are some challenges to face when we adopt the microservices architectural style. The first one handles operational complexity; services such as service discovery and load balancer help us to tackle these points. We solved these challenges in the previous chapters and got to know some important tools while doing so.
There are some other important key points to handle in microservices adoption. The effective way to monitor what happens in our microservices environments is to monitor how many times microservices consume other microservices resources, such as HTTP APIs, and how many times they fail. If we have near real-time statistics, it can save the developer days of troubleshooting and error investigations.
