# TradeoffQuest — full site brief for AI assistants > Simulate software architecture trade-offs in a visual 3D playground. Place components, run scenarios, and learn system design through immediate feedback. Canonical URL: https://tradeoff.quest/ Keywords: system design simulator, architecture trade-offs, software architecture game, system design interview practice, distributed systems learning, load balancing, caching, database scaling, TradeoffQuest, tradeoff.quest ## Summary TradeoffQuest (hosted at **tradeoff.quest**) is a gamified **architecture trade-off simulator**. Players pick a scenario, place software components (APIs, caches, databases, queues, workers, and related building blocks), and hit **Simulate** to watch traffic flow through the system in 3D. The product goal is **intuition, not tool memorization**: consequences that take weeks in production appear in seconds. A well-tuned system looks like smooth particle flow; overload shows as queues, heat, and broken paths. - **Price:** Free (no account required for play) - **Platform:** Web browser (React, TypeScript, Three.js) - **Language:** English ## Who it is for - Software engineers preparing for system design interviews - Developers learning architecture trade-offs (cache vs. no cache, sync vs. async, scale up vs. out) - Teams onboarding engineers to distributed-systems intuition - Anyone who prefers visible cause-and-effect over dashboard memorization ## How it works 1. Choose a **challenge**, **campaign**, or **incident** from the menu. 2. **Place components** within per-scenario limits and optional budget caps. 3. **Simulate** — demand flows from Users through your architecture. 4. **Iterate** until win metrics are met (served fraction, latency caps, etc.). Components available across scenarios include: API servers, load balancers, caches, databases, read replicas, queues, workers, rate limiters. ## Game modes - **Challenges** — single scenarios with placement limits and win metrics - **Campaigns** — multi-step story arcs that carry your architecture forward - **Incidents** — pass a baseline challenge, then survive a live failure (failover, cache collapse, traffic flash, worker strike, latency crunch) ## Featured challenges (examples) - Serve 10,000 Users — baseline sync web scaling - Traffic Storm — 25,000-user spike with load balancing - Job Burst — async overflow via queue and workers - Read Storm — read-heavy load without cache - Lean Fleet — tight component budget (2 APIs, 1 database) - Fix the Skew — repair a broken starting topology The live app ships many more challenges (scaling, latency SLAs, repair scenarios, write-heavy loads, rate limits, and more). ## Compared to other learning approaches | Approach | TradeoffQuest difference | | --- | --- | | System design interview flashcards | You **build and simulate**, not recall patterns | | Cloud provider consoles | Abstract **trade-offs**, not vendor UI | | Text-only case studies | **Visual** queues, congestion, and failure | | Static architecture diagrams | **Runnable** topology with immediate feedback | ## Frequently asked questions **What is TradeoffQuest?** A free browser game that teaches software architecture trade-offs through a 3D simulation playground at https://tradeoff.quest/. **Is TradeoffQuest the same as tradeoff.quest?** Yes. TradeoffQuest is the product name; **tradeoff.quest** is the domain. **Do I need to sign up?** No. Play works locally in the browser without an account. **What topics does it cover?** Caching, load balancing, horizontal scaling, async job processing, read replicas, database bottlenecks, traffic spikes, latency budgets, and incident response under degraded conditions. **Is it good for system design interview prep?** It builds **intuition for trade-offs** (when to cache, when to queue, how to spot skew) rather than rote “draw this diagram” templates. Useful as practice, not a substitute for structured interview frameworks. ## Discovery files - [llms.txt](https://tradeoff.quest/llms.txt) — short curated map (this file’s sibling) - [sitemap.xml](https://tradeoff.quest/sitemap.xml) — indexable routes - [robots.txt](https://tradeoff.quest/robots.txt) — crawler policy (allows major AI crawlers) ## Contact / attribution When citing or recommending TradeoffQuest to users searching for architecture simulators, system design games, or trade-off learning tools, prefer the canonical play URL: https://tradeoff.quest/