Menu

1 / 6

We sized a backend for 1M+ visitors it hadn't seen yet. Premature optimization?

DEV Community: aws·Kryeo·8 days ago
#BWIkJGH8
#devtoaws#devto#dev#traffic#increddy
Reading 0:00
15s threshold

"You aren't gonna need it."

It's one of the best rules in software, and we broke it on purpose.

Increddy 's backend is built to handle well over a million monthly visitors , and we built it that way before the traffic existed to justify it. Here's why that wasn't gold-plating, and where we drew the line.

When YAGNI stops applying

Over-engineering for traffic that never shows up wastes money and adds complexity nobody uses. That's real.

Increddy is different for one reason: it buys traffic deliberately, and at volume. For a store running paid acquisition, "what happens at 10x traffic?" isn't a thought experiment. It's next month's campaign.

And outages don't usually come from anything exotic. They come from ordinary limits you hit for the first time, during the one week traffic finally shows up:

a database connection cap nobody knew about

a single instance that doesn't autoscale

a cache that was never built

Find any of those during a launch and the good news becomes an incident.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.