Hacker News Reader

"The modularized monolith can be scaled horizontally as well, but you scale out all modules together."

That's not exactly true. Yes you probably have to ship the whole monolith, but who said that you also have to get traffic for all the parts? For example you have /users/ and /books/. You can configure your nodes to only serve /users/ and configure different (maybe more) nodes to serve /books/. The code sits there but who cares?

View on HN

We did this at my last gig. The application was monolithic[1] but ran in multiple environments: web application, API, admin, backend workers.

It worked quite well. The one downside is we had to load all the code (it was Rails) so processes took more RAM than strictly necessary. But sharing data models across all these services was pretty easy.

[1] There were a few separate services, for example a documentation CMS.

Absolutely, also see my other reply along these same lines: https://news.ycombinator.com/item?id=13960837

Reply on news.ycombinator.com