Hacker News new | ask | show | jobs
by brodouevencode 634 days ago
There's the ideal path, then the actual. Most monoliths, unchecked and with enough age, turn into spaghetti due to turn over, changing priorities, entropy, etc.
3 comments

In my experience same goes with microservices. Same spaghetti, different abstraction layer,
you are correct
But at least some microservices architectures turn into macaroni - far too many small, isolated things, with no connection between them. It can have all the disadvantages of an overly-OO design, just at a larger scale.
The majority of microservice architectures end up being distributed monoliths.