Microservices rules #10: Make smaller, safer, and reversible changes - part 2
This is the fourth article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively.
The other articles in the series are:
- Microservices rules #2: Implement fast, automated deployment pipelines
- Microservices rules #5: Deliberative design
- Microservices rules #10: part 1 - incremental architecture modernization
In the previous article, I described why it’s important to break what would otherwise be a big, risky and difficult to reverse change to your application, into a series of smaller, safer, and reversible changes. I also discussed how to apply this idea to application modernization. In this article, I describe how to apply this idea to the outer developer loop: continuous delivery and deployment.