Microservices rules #11: Track and improve metrics
This is another article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively. 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
Using the microservice architecture can be challenging. You must make numerous architectural design decisions that can be very consequential, even small missteps can have far-reaching impacts. You can minimize the risk of making bad decisions by using Microservices rules #5: Deliberative design and Microservices rules #10: Make smaller, safer, and reversible changes. But there’s always a chance that something will go wrong especially if it’s your first time using microservices. Consequently, it’s essential to follow Microservices rules #11: Track and improve metrics.
In this article, I outline three key categories of metrics you should track to ensure your microservices development stays on course.
