Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That push to fragmentation is in large part because of hard lessons learned from the problems of a monolith.

The answer is IMO somewhere in between. Microservices can get too tiny and thus the system becomes impossible to understand. However a monolith is impossible to understand as well.

The real problem is you need good upfront architecture to figure out how the whole system fits together. However that is really hard to get right (and Agile discourages it - which is right for small projects where those architects add complex things to mitigate problems you will never have)



Monolith != Monorepo. They're independent concepts.


I work at a company that has several micro services and a backend all in one monorepo. For some anecdata.


The tooling defaults around Github encourage having one thing per repo.


A monolith can (and often does) consist of separately versioned libraries.





Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: