3 ms·
Monoliths have their role in the world, certainly! I've heard Facebook have a mantra of sorts about their monolith, if anyone here could corroborate that would
by dayjah 11y ago
Monoliths have their role in the world, certainly! I've heard Facebook have a mantra of sorts about their monolith, if anyone here could corroborate that would be great. It goes something like:
- build v1 in the monolith
- do users like v1?
- if so, does v1 use too much of the monolith?
- improve the implementation within the monolith
- does it still use too much of the monolith? Break it out into its own stack
I believe there are only two stacks:
- ad serving, where literally lower latency is more money and thus benefits from optimizations not realistic within the monolith,
- and "everything else".
- ghaff 11y agoMartin Fowler has argued for something similar. [1] I suspect that the "right" answer is complicated and based on things like where you're coming from, the size of team(s), and the degree to which there are well-defined shared services. DHH of Basecamp also argued recently [2] that Monoliths can make sense although I noted at the time that, with a team size of about 12 engineers, that isn't much larger than the two-pizza team sizes you see promoted for microservices functions. [1] http://martinfowler.com/bliki/MonolithFirst.html http://martinfowler.com/bliki/MonolithFirst.html [2] https://m.signalvnoise.com/the-majestic-monolith-29166d022228#.3npyzyfsr https://m.signalvnoise.com/the-majestic-monolith-29166d02222...
- Touche 11y agoAlso known as "we'll fix it later".