Interactive Build (In Progress)

Production Panic

A browser-based incident-response game built with React where players triage cascading backend alerts, balance system stability against engineering capacity, and make rapid architectural trade-offs under pressure.

React TypeScript Deterministic State Reducers CSS Grid Vite
DEPLOYMENT STATUS

Associated with satyabuildsbuilds.com (domain associated; live deployment URL pending verification). The live action button remains suppressed until the deployed URL is verified in src/config/site.ts.

TICK SCHEDULER Deterministic Step GAME STATE REDUCER Latency · Error Budget Incident Queue REACT TELEMETRY HUD Keyboard & Touch Triage Controls
ARCHITECTURAL SCHEMATIC (NOT A FAKE APPLICATION SCREENSHOT) — DETERMINISTIC STATE LOOP

Why the Project Exists

Backend engineering involves constant trade-offs during degraded states: scaling read replicas takes time, flushing a cache spikes database CPU, and rolling back a deployment might drop in-flight events. Production Panic turns those real operational tensions into an accessible, fast-paced browser simulation.

How the Game Works

Rather than relying on twitch reflexes, gameplay centers on diagnosing symptom patterns and choosing mitigation actions before the system's error budget is exhausted:

  • Incident Queue: Incoming events (e.g., connection pool saturation, cache stampede, downstream broker lag) accumulate with varying severity trajectories.
  • Resource Trade-Offs: Every response action consumes responder focus or temporary system capacity, preventing players from spamming every mitigation simultaneously.
  • Feedback Loop: System health metrics update per simulation tick so players see the secondary consequences of their decisions.

Engineering Implementation

Browser games built in React can easily suffer from stale closures in timer loops and excessive component re-renders. The architecture addresses this through:

  • Pure Reducer State Transitions: Game ticks and player actions dispatch into a deterministic reducer function, making state transitions predictable and unit-testable in isolation from the DOM.
  • Scoped Render Boundaries: High-frequency tick indicators are isolated from static layout panels so React only reconciles changed telemetry readouts.

UI and Mobile Considerations

Dense monitoring dashboards rarely translate well to narrow mobile screens. Instead of shrinking a multi-panel desktop layout onto phones, the responsive layout prioritizes a single active triage stack with touch-friendly action buttons (minimum 44px hit targets) and full keyboard shortcut parity on desktop.

Implemented Scope vs. Planned Improvements

Implemented Foundation

  • Core reducer-driven simulation loop and incident state transitions.
  • Responsive dashboard layout with keyboard and touch controls.
  • Configurable scenario definitions for testing difficulty balance.

Planned Next Steps

  • Post-incident replay timeline showing root-cause decision branches.
  • Additional polyglot persistence and message-broker failure scenarios.
  • Public verification and linkage of the satyabuilds.com deployment.

Related Work