Microservices rules #9: Develop observable services
architecting observability microservices rulesContact me for information about consulting and training at your company.
The MEAP for Microservices Patterns 2nd edition is now available
This article continues the series on microservices rules: what good looks like, a collection of principles and practices that help teams adopt microservices successfully.
The articles in the series are:
1. Practice continuous delivery/deployment
2. Implement fast, automated deployment pipelines
4. Provide a great developer experience (DevEx)
5. Use a deliberative design process
6. Design independently deployable services
7. Design loosely coupled services - part 1, part 2, part 3
9. Develop observable services
10. Big/risky change => smaller/safer and (ideally easily) reversible changes - part 1 - incremental architecture modernization, part 2 - continuous deployment, part 3 - canary releases, part 4 - incrementally migrating users, part 5 - smaller user stories
11.Track and improve software metrics and KPIs
Microservices rules #9 is Develop observable services, the fourth of four architectural rules:
This article explains why observability is important, how it enables fast flow, and how to design observable services.
Premium content now available for paid subscribers at 
