Stats-Coronavirus_

The Problem

At the start of the pandemic, the information problem was obvious: people needed one fast place to check evolving case numbers without waiting on slow dashboards or overloaded APIs. That meant the system had to prioritize resilience and read performance over architectural elegance.

The Architecture

The design was intentionally simple on the hot path. Data was pulled from public sources, normalized during ingestion, and pushed into Redis so the read layer could serve precomputed answers instead of building them on demand.

The React frontend stayed mostly presentation-focused, while the API behaved more like a cache delivery layer than a traditional application backend.

What Mattered Technically

• normalize once during ingestion instead of computing on every read
• keep Redis on the hot path for fast lookups
• avoid unnecessary moving parts during a global traffic event
• serve a frontend that could stay static and cache-friendly

This was a case where simplicity was the advanced move. Under extreme traffic, fewer moving pieces often beat more sophisticated architecture.

That lesson still holds. If the read path has to survive unusual public attention, precomputation and cache discipline matter more than architectural ornament.