Hacker News Reader

People went full monoliths to full microservices.

The same people are now saying creating microservices is a sign of incompetence and the smart thing to do is create monoliths.

But not to sound ridiculous, they bring a spin to it: they now say they create modules within the monolith.

Software engineering is like fashion. It goes full circle every X years.

View on HN

It should be: start with a well architected monolith, and then slice things into microservices when you need to. Fowler and many Microservice evangelists even say to start with a monolith first, because you don't know the correct slices at the beginning.

EDIT: I suck at writing coherent messages on my phone.

Meanwhile, the experienced/good/non-charlatan engineers endorse choosing the right architecture for the job. Building a CMS? You probably want a pretty large monolith. Also building an analytics platform? That should probably be a separate service aligned to a different team.

Reply on news.ycombinator.com