Practice/Meta/Design Online Chess

Design Online Chess

Product DesignMust

Problem Statement

Design a platform for hosting real-time multiplayer card games similar to Hearthstone or Legends of Runeterra. The system must support thousands of concurrent games where players can create matches, join lobbies, play cards in turns, and see opponent actions with minimal latency. The platform should handle player matchmaking based on skill ratings, maintain game state consistently across devices, and store complete game history for replay and analysis. Consider that each game involves complex state with deck configurations, card effects, animations, and turn-based mechanics where players alternate actions with strict timing constraints.

The system must gracefully handle network disruptions, prevent cheating through client-side manipulation, and scale to support millions of daily active users across web and mobile platforms. Games typically last 10-20 minutes with frequent state updates as cards are played, effects trigger, and boards evolve.

Key Requirements

Functional

• Game lobby management -- players create or join game rooms with configurable rules and invite friends or use matchmaking
• Real-time gameplay -- synchronize game state between players as they play cards, attack, and trigger abilities with sub-second latency
• Turn-based coordination -- enforce turn order, action windows, and timeouts while maintaining fairness
• Persistent game state -- save in-progress games for reconnection and maintain complete match history
• Matchmaking system -- pair players of similar skill levels using rating algorithms like ELO or Glicko
• Spectator mode -- allow observers to watch live matches without impacting gameplay

Non-Functional

• Scalability -- support 100,000+ concurrent games with peaks of 500,000+ daily active users
• Reliability -- achieve 99.9% uptime with automatic failover and state recovery mechanisms
• Latency -- deliver action updates to opponents within 200ms under normal conditions
• Consistency -- guarantee strong consistency for game state to prevent divergence or cheating exploits

What Interviewers Focus On

Based on real interview experiences, these are the areas interviewers probe most deeply:

1. Real-Time State Synchronization

The core challenge is keeping game state consistent between two or more players while maintaining low latency and preventing cheating. Unlike chess where moves are simple, card games involve complex chains of effects, animations, and state transitions.

Hints to consider:

• Consider whether WebSocket connections or server-sent events better suit bidirectional real-time communication
• Explore authoritative server patterns where the server validates all actions before broadcasting to prevent client-side cheating
• Discuss optimistic updates on the client for perceived responsiveness while awaiting server confirmation
• Think about conflict resolution when network partitions cause temporary divergence

2. Game State Storage and Recovery

Players expect to resume games after disconnections or app crashes. The challenge is determining what state to persist, how frequently, and how to efficiently reconstruct game state on reconnection.

Hints to consider:

• Evaluate event sourcing patterns where you store each action as an immutable event rather than snapshots
• Consider hybrid approaches combining periodic snapshots with incremental event logs for fast recovery
• Discuss trade-offs between storing full state in memory databases like Redis versus disk-based persistence
• Think about how replay functionality leverages stored game history

3. Matchmaking Algorithm and Queue Management

Pairing players quickly while maintaining competitive balance requires sophisticated queue management. The system must balance wait time against match quality.

Hints to consider:

• Explore rating systems like ELO, Glicko, or TrueSkill for quantifying player skill
• Discuss widening search ranges over time to balance match quality against wait time
• Consider separate queues for casual versus ranked play with different matching criteria
• Think about how to handle parties or groups queuing together with individual skill variations

4. Handling Network Disruptions and Reconnection

Network issues are common in mobile gaming. The system must detect disconnections, preserve game state, and allow seamless reconnection without punishing players for temporary connectivity problems.

Hints to consider:

• Design heartbeat mechanisms to detect connection loss versus intentional abandonment
• Discuss grace periods where games pause awaiting reconnection versus forfeiture
• Consider how to prevent abuse where players disconnect strategically to avoid losses
• Think about bandwidth-efficient state transfer when reconnecting mid-game