Microservices rules #8: Design testable services
This article continues the series on microservices rules: what good looks like, 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 #8 is Design testable services, the third of four architectural rules:
This article explains why testability is essential for achieving fast flow, why it isn’t guaranteed in a microservice architecture, and how to design microservices that support it through deliberate design.