[curious_cat_163]

Yes. It does require thinking about the monolith in a way so it can be broken up should the need arise.

Going down the monolith path != Having spaghetti as the core abstraction. :)

[brodouevencode]

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.

[two_cents]

In my experience same goes with microservices. Same spaghetti, different abstraction layer,

[brodouevencode]

you are correct

[AnimalMuppet]

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.

[kgeist]

The majority of microservice architectures end up being distributed monoliths.