Microservices rules #10: Make smaller, safer, and reversible changes - part 3
This is the fifth 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
- Microservices rules #10: part 2 - continuous delivery/deployment
In the previous two articles, 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 covered how each developer should strive to break their work into small, incremental changes that are deployed to production at least once a day.
In this article, I how to use the concept of smaller, safer, and reversible changes to update production by incrementally shifting traffic to the new version of a service.