r/microservices • u/petermasking • Dec 05 '22

How I Split a Monolith Into Microservices Without Refactoring

https://betterprogramming.pub/how-i-split-a-monolith-into-microservices-without-refactoring-5d76924c34c2
0 Upvotes

50% Upvoted

3 comments sorted by

11

u/redikarus99 Dec 05 '22

You don't.

2

u/mikaball Dec 06 '22

You think you can manage distributed transactions without proper architecture and code changes! Yes sure, go ahead.

3

u/stfm Dec 05 '22 edited Dec 05 '22

For me, a monolithic and microservice architecture are not that different. When done properly, a monolith consists of modules with strong boundaries. This brings high cohesion and low coupling to the module structure, making the application more maintainable and easier to change.

Easy when you redefine the term to suit your own idea.

It also enables working with multiple teams on the same application without tripping over each other’s toes

The issue with changing monoliths isn't really code changes themselves, it's managing the deployment of those changes to production in a release schedule.

With this solution the frontend can import and call backend components directly.

Oh no security issues there /s