Serving 39 Million Requests for $370/Month, or: How We Reduced Our Hosting Costs by Two Orders of…
Adam Pash
53013

It’s a really interesting read, but the one thing that I think would help the article more than anything is if you could break down just how much of your previous cost were from the database change.

You mention going from a database that stored a massive slice of the internet to losing the database entirely in favor of a short term cache. Before even looking at costs of storage, backups, redundancy, disk I/O and what I assume was probably another cache as well…it seems like that would have to account for a very significant portion of your savings.

It’s hard to read an article like this and not wonder “was it Lambda…or the database change where the savings really came from?”

Show your support

Clapping shows how much you appreciated Barry Jones’s story.