Big decisions: creating a monolith to microservices modernization plan
This article is the third in a three part series that describes a decision-making framework for determining whether to migrate an application to the microservice architecture:
- Part 1 - identifying reasons to migrate your monolith to microservices
- Part 2 - identifying reasons to stay with the monolith
- Part 3 (this article) - creating a monolith to microservices modernization plan
In part 1 and part 2 of this series, I described how to first determine whether it makes sense to migrate your monolith to microservices and then, if it does, how to identify candidate changes.
In this article, I how to create a migration plan for doing the work of migrating to the microservice architecture. The plan defines the order in which you will implement the candidate change.