Something people use to architect towards being the next Amazon, before they've even got their first 100 users. Also useful for CV padding.

Genuinely useful method for abstraction, concern/dependency separation, scaling, and so forth, for teams & projects that genuinely need what they offer.

Or build core infrastructure right the first time, and not spend millions of dollars turd-polishing while your competition eats the market.

Davids talk makes some good arguments, but does not fully acknowledge low-maintenance infrastructure at scale. =3

"10 tips for failing at microservices" (David Schmitz)

https://www.youtube.com/watch?v=GWgRw5jiYy0

[dead]