2 ms·
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. Microserv
by bluGill 1y ago
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)
- jyounker 1y agoMonolith != Monorepo. They're independent concepts.
- MiscCompFacts 1y agoI work at a company that has several micro services and a backend all in one monorepo. For some anecdata.
- datadrivenangel 1y agoThe tooling defaults around Github encourage having one thing per repo.
- layer8 1y agoA monolith can (and often does) consist of separately versioned libraries.
- cmrdporcupine 1y agohttps://askastaffengineer.com/ https://askastaffengineer.com/