Part 3. Handling cross-cutting concerns: building a reusable microservice platform

In this part, you’ll build a platform that handles some important cross-cutting concerns and that’s ready to be used across many microservices. The cross--cutting concerns you’ll implement include monitoring, logging, passing correlation tokens along with requests between microservices, and security concerns around microservice-to-microservice requests. All these concerns make microservices behave well in production. With them in place, you can gain insight into the health of each microservice and trace business transactions across microservices.