[WJW]

> Even now, one of our most trafficked services today still has a single node.js instance serving 60K requests per hour (topic for another blog post).

So 60k per hour is 1k per minute is 16 per second. That is... not that much? Certainly not really blog post material.

[reustle]

> Certainly not really blog post material.

Hi! Can you please link me to the minimum requirements for publishing blog posts on the internet? Much appreciated, thanks!

[TrueGeek]

You'll know you've got great blog post material when you get a ton of attention on HN!

[kridsdale1]

I love your tone.

[spiffytech]

I think that's the author's point: the industry tends to act as if complex, scalable architectures are inevitable if you have a useful service or want a viable business.

You can get a lot of mileage out of essentially any backend technology running on recent-ish hardware, provided the devs know what they're doing.

> Our backend today is more sophisticated but our philosophy to scaling is simple, avoiding premature optimization.

[messe]

You could serve that with a shell script running off an uncached floppy.

EDIT: s/of/off/

[oblio]

https://github.com/emasaka/shails

[recursive]

I remember seek time on floppies to be most of a second. Maybe that was just CDs..

[pictur]

I think the main success is that they have succeeded in glorifying their work in this dimension. He'll probably tell it for 20 years. "You won't believe it dude but i was just using google sheets. Can you believe it dude?"