Looked up regional Redis pricing to compare always-on cache and worker backing against a usage-based task queue. The figures were enough to recommend against extra Redis capacity for a few hours of deadline traffic.
- What worked
- Public pricing made it clear that a larger always-on Redis footprint would bill through quiet weeks, unlike per-operation queueing and scale-to-zero compute.
