insignificant

1/ LagosLife crossed 2M+ players within days of launch, with millions of visits daily and six-figure concurrent-user peaks. And despite that completely unexpected growth, it has mostly remained responsive. As a developer, I became more interested in how it survived the traffic than the game itself. So I spent some time looking at the public clues around its infrastructure. This is my attempt to reconstruct what may be happening behind LagosLife. Important: this is observation and inference, not a confirmed teardown. I don’t have access to their source code or infrastructure dashboard, and I could absolutely be wrong about parts of this. But the clues are interesting. 🧵 2/ The strongest clue comes from LagosLife itself. Their privacy policy says Cloudflare hosts both the game and its database. Public fingerprinting also points towards React + Next.js. That immediately changes how I think about the backend. I don’t think we’re looking at the conventional architecture many of us would reach for: Browser → Next.js → Node API → nginx → VPS → PostgreSQL My suspicion is that LagosLife is far more Cloudflare-native. Something closer to: Browser → Cloudflare Edge → Workers → Cloudflare-managed storage/realtime primitives Which is a very different scaling model. 3/ My rough reconstruction of the backend looks something like this: Browser ↓ Cloudflare Edge ↓ Cloudflare Workers ↓ Then some combination of: • D1 for persistent state • Durable Objects for realtime state/presence • KV or R2 for cache/assets/data • Queues for asynchronous work • external payment infrastructure Only part of that is confirmed. Cloudflare hosting is confirmed. The specific services underneath are my inference based on the workload and the way Cloudflare’s platform is designed. But the exact products matter less than the architectural principle I think LagosLife is using: the backend probably does surprisingly little work per player. 4/ This is the part I think explains most of the scaling story: LagosLife appears to be very client-heavy. Think about the actual game loop. Your character walking across the screen doesn’t need a database query. Animations don’t need the backend. Need bars counting down don’t need the backend. UI interactions don’t need the backend. Rendering the city doesn’t need the backend. Timers don’t need the backend. Cached world data doesn’t need the backend. A huge amount of what makes the game feel alive can happen entirely inside your browser. That means 100,000 people actively playing does not automatically translate into 100,000 people continuously hammering the backend.