Hacker News Reader

I totally agree that one should start with a monolith and when he feels confident that all bases were covered in the codebase, he can begin to worry about breaking up the monolith into microservices.

This growth journey makes more sense than starting out the door working on your microservices before business logic as this is like putting the cart before the horse.

View on HN

Even then, I have a feeling that people jump too quickly from a "messy monolith" to microservices.

Instead, people should start splitting up the monolith into sensible modules and libraries. Instead of a "user accounts microservice", start with a "user accounts library" with a well-documented API that stays in the main codebase and is deployed as part of the rest of the app.

Reply on news.ycombinator.com