4 ms·
The contempt towards the “old ways” in this piece is really irksome, especially since those “old ways” are perfectly acceptable for 95% of applications (you onl
by orev 5y ago
The contempt towards the “old ways” in this piece is really irksome, especially since those “old ways” are perfectly acceptable for 95% of applications (you only need this hyper scale stuff if you’re running a MAANG level app). The rest of us still doing things the “old way” are perfectly happy to have simple systems that run reliably, as we sit and watch the complete train wreck of complexity everyone else is building using these “new ways” that are supposedly better.
- iwintermute 5y agoI know it's off-topic but maybe "MAANG level app" >> "MANGA" if we want go there?
- 6gvONxR4sf7o 5y agoIf you're going to rename F to M, why not rename G to A?
- pred_ 5y agoBut if F->M, then why not G->A? MAAAN.
- robsutter 5y agoI actually think this piece aligns with your thinking. Using a single, strongly consistent data store to eliminate the "train wreck of complexity" allows for a better developer experience while still delivering a responsive user experience. That matters at all kinds of scale, not just hyper.
- chrisjc 5y agoWhile I see your point, it really felt like they were trying to empathize with "new" developers that might feel that way about doing things the "old way"... and that they may want to reconsider those feelings now that there are new technologies and services to overcome the limitations that existed in the "olden times".