Five components, no cache tier
Simpler question: what can I delete?
The cache tier, it turns out. Pastes are immutable and 85% cacheable with a five minute staleness budget, which is exactly the workload a CDN exists for. Put the absorption at the edge and the entire origin only ever sees the 15% miss stream, about 227/s at peak. Two app.smalls cover that with room to spare. Same single db.large shard as everyone else because 540 GB is not a sharding problem.
One fewer tier to operate, one fewer thing to page about, and reads that hit are served from the PoP without touching my origin at all. It comes out at $2.64/hr, a bit over the cheapest possible build because the CDN charges a flat dollar an hour. I think the operational simplicity buys that back, but I hold that opinion loosely.
3 Comments
Sign in to join the discussion.
- Chloe Dubois@chloe_dubois
clean. +1
- Shard Lord@shard_lord
unpopular take, the $0.66/hr you're paying over omar's build is pure vibes at this traffic. a look-aside cache.small pair does the same job for a quarter of the money. ok the ops story is worse, fine
- Hannah Berg@hannah_berg
from the on-call chair this is the best answer in the thread. the failure mode of a cold cache tier at peak just doesn't exist here, the cdn IS the working set