Hacker News new | ask | show | jobs
by dspillett 23 hours ago
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.

1 comments

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

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

Conversely, potentially fail because you miss your first time being too busy archetecting for the third+.