Full title: Mitosis Pattern: Scale software while avoiding becoming a legacy monolith without falling into the microservices trap
Just as improvement should be iterative, software plan should change erstwhile the context and our knowing of the problem evolve. As a software grows to solve more problems, it becomes little supple in its ability to evolve. Tensions arise within the business model of the software that struggles to stay coherent. yet it reaches a critical mass and becomes a monolith of spaghetti code. How do we know erstwhile it’s time to modularize our software? How do we carry on the decision to divided it into respective modules or services? How can we handle the progressive differenciation of our business models while avoiding unnecessary coupling? It’s not as easy as a clean axe cut in the middle, uncovering the right boundaries can be tricky. We would like to introduce the Mitosis Pattern, a dynamic approach utilized to divided a business model into multiple ones that will get shaped and decoupled iteratively. Gain flexibility to choose better erstwhile to divided into multiple services, and avoid paying the scale cost of microservices or becoming a distributed monolith.
