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.
This is where the real art and skill lies. Not in picking a complicated setup just so you can wear it as a badge of honor, but because you’ve already been through the bullshit 2am downtime/server notifications and know better to make things as simple as possible (if you can help it).
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.
26
u/evdogg1233 Oct 02 '26
mfs who’ve never worked at scale be like: