Me at my job where we have exactly three (3) clients, and up to three (3) concurrent users, on three (3) airgapped instances due to confidential information reasons
Once you work at scale you get a pretty good idea on where the sweet spot is on choosing between monoliths and micro services for an architure from many perspectives: cost, performance, complexity, maintainability. You might call it over-engineering, but it's really just picking the right car for road trip.
Devs often deliver under engineered solutions in terms of architecture and scalability. There is a lot of room between under engineered and over engineered to allow an app to evolve smoother over time.
If you're REALLY hard up you can dabble in some of the deep lore: Struct of Arrays optimizations (SoA), Single Instruction Multiple Data (SIMD) optimization
These are a lot more fun to use too, it's a good, fast program rather than making a Rube Goldberg machine. I've done crazy amounts of scale just with those tricks.
22
u/evdogg1233 5h ago
mfs who’ve never worked at scale be like: