3 ms·
Splitting code into modules has the same downsides as splitting it into microservices. You can still end up making the wrong splits and needing to back track on
by Philip-J-Fry 5y ago
Splitting code into modules has the same downsides as splitting it into microservices. You can still end up making the wrong splits and needing to back track on things you once thought were modular but no longer are.
The logistics of microservices are rarely the hard part. It's the long term maintenance. Everyone who's ever maintained a "core" library knows the same pain, at some point you just end up making sacrifices just to get things to work.
- discreteevent 5y ago> Splitting code into modules has the same downsides as splitting it into microservices. Not to be pedantic, but it has some of the same downsides. Microservices have other major downsides in that they bring in all the fallacies of network computing. Even if you manage to stabilize these in the end they just waste so much time in development and debugging.