Preparing the next view without exposing private workflow data.
Performance engineering · Phased project
Keep product availability caching correct during a traffic spike
A fictional equipment-rental service caches availability summaries. A campaign sends repeated reads, while stock updates and shared expiry times create bursts against the origin. Build a local origin stub and cache-backed read API using synthetic depots and products.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
33h 45m + setup
Suggested stack
TypeScript · Redis · HTTP · k6
Recommended next step
Start with PCACHE-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Learn to evaluate caching through avoided work, bounded staleness, concurrency and recovery rather than hit rate alone.
What the team gains
Produce a reviewable cache policy and failure exercise for a read-heavy service with changing business data.
Before you start
Create a deterministic local availability origin and Redis-backed reader with synthetic tenant, depot and product data.
Use a seeded hot-key distribution and controlled time; record cache capacity, TTLs, runtime and machine limits.
Delivery agreement
Ten tickets in three phases. Availability is informational; booking remains an authoritative origin operation. All load and failure experiments use owned local services.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.