9 ms·
Whenever there are discussions about scaling and performance, I think it is useful to at least reference the TechEmpower benchmarks as a data point. https://www
by wbond 12y ago
Whenever there are discussions about scaling and performance, I think it is useful to at least reference the TechEmpower benchmarks as a data point. https://www.techempower.com/benchmarks/#section=data-r9&hw=peak&test=query https://www.techempower.com/benchmarks/#section=data-r9&hw=p...
In terms of scaling, I've observed that many engineering organizations drop the idea of full-stack or monolithic anything for a couple of reasons. The first is understanding all of the major constituent parts of their system, and secondly to make it easier to replace any part that is identified as a bottleneck.
- hkarthik 12y agoI'll add that many engineering organizations also began to drop the idea of full stack development as they grow and split up into independent, semi-autonomous teams. When you have 300 engineers writing code into one monolithic code base, a lot of the advantages of a monolith become major liabilities. You can throw a lot of process and tooling at it, but eventually it slows you down enough to the point where splitting things apart makes far more sense.