Scale Game

Scale Game

Overview

Test your approach at extreme scales to find what breaks and what surprisingly survives.

Core principle: Extremes expose fundamental truths hidden at normal scales.

Quick Reference

| Scale Dimension | Test At Extremes | What It Reveals | |-----------------|------------------|-----------------| | Volume | 1 item vs 1B items | Algorithmic complexity limits, index needs | | Speed | Instant vs year-long | Async requirements, caching needs, timeouts | | Users | 1 user vs 1B users | Concurrency issues, resource limits, auth bottlenecks | | Duration | Milliseconds vs years | Memory leaks, state growth, data rot | | Failure rate | Never fails vs always fails | Error handling adequacy, retry logic | | Data size | 1 byte vs 1TB | Storage strategy, streaming vs buffering |

Process

1. Pick dimension — What could vary extremely?
2. Test minimum — What if this was 1000x smaller/faster/fewer?
3. Test maximum — What if this was 1000x bigger/slower/more?
4. Note what breaks — Where do limits appear?
5. Note what survives — What's fundamentally sound?

Examples

Example 1: Error Handling

Normal scale: "Handle errors when they occur" works fine At 1B scale: Error volume overwhelms logging, crashes system Reveals: Need to make errors impossible (type systems, contracts) or expect them (chaos engineering, circuit breakers)

Example 2: Synchronous APIs

Normal scale: Direct function calls work At global scale: Network latency makes synchronous calls unusable Reveals: Async/messaging becomes survival requirement, not optimization

Example 3: In-Memory State

Normal duration: Works for hours/days At years: Memory grows unbounded, eventual crash Reveals: Need persistence or periodic cleanup — cannot rely on process memory

Example 4: Single DB Write Path

Normal load: One writer, no contention At 10k concurrent writes: Deadlocks, lock contention, queue buildup Reveals: Need optimistic locking, write batching, or event sourcing

Red Flags You Need This

• "It works in dev" (but will it work under production load?)
• No idea where the limits are
• "Should scale fine" (without testing or analysis)
• Surprised by production behavior
• First time this code will see real users

Remember

• Extremes reveal fundamentals
• What works at one scale often fails at another
• Test both directions (bigger AND smaller)
• Use insights to validate architecture early — cheaper to change now

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: danielleit241
• Source: danielleit241/forge
• License: ISC

Install and usage instructions live in the source repository linked above.