Big decisions: Should you migrate your monolith to microservices? Part 2

This article is the second 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 (this article) - identifying reasons to stay with the monolith
- Part 3 - creating a monolith to microservices modernization plan
In the previous article Big decisions: should you migrate to microservices? Part 1 I described how to use the dark energy forces to determine whether there’s a justification for migrating your monolith to microservices and identify candidate change requests for migrating subdomains to services. In this article, I’ll describe how to evaluate the feasibility of those change requests using the dark matter forces.