[sneak]

Yeah, the whole article seemed “webscale for webscale’s sake”, despite describing a product just a few steps beyond MVP.

Overengineering abounds. It’s easy to feature flag something and roll it out only to a fraction of the userbase and see if the database falls over, or if you’re biased toward acronym/resume-driven-development.

We’re almost certainly talking about megabytes here, not terabytes.

[et1337]

This line at the end of the article triggered me:

> You can invest [your spare time] each week towards something bigger like a pub/sub system so that you can pull a new microservice out of your monolith.

[danielmarkbruce]

But it's such a great idea. You too can soon have 700 microservices.