7
Microservice Observability
In the last chapter, we were able to orchestrate the MTAEDA application so that it is easy to launch and debug all the components of the system. Every individual service is available for interrogation at runtime, so it is easy to identify issues and gain the necessary insight to resolve them.
Eventually, the MTAEDA application will reside in several other environments outside of active development. When the application doesn’t work as expected, it is vital to be able to observe what is going on internally. Classically, monolithic applications produce cohesive serial logs that can be observed as needed.
Observability is critical to the speed of the overall development life cycle in quality assurance and user acceptance ...
Get Implementing Event-Driven Microservices Architecture in .NET 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
