Databases for Server Side Game Developers
Databases for games is choosing how to store player data and game state. It covers modelling profiles, progression and inventories in relational or document stores, and event sourcing, where state is derived from an append-only log of events, giving history, audit and the ability to rebuild state.
Stage: Data and Persistence · Part of the Server Side Game Developer roadmap · Last reviewed 19 November 2026
What to learn in Databases
- Model a player profile and inventory in a relational schema
- Compare SQL, document and key-value stores for player data
- Handle schema changes for live data without downtime
- Write an append-only event log and rebuild state from it
- Use optimistic concurrency to avoid lost updates
- Plan sharding of player data by player id
Databases interview questions
What is event sourcing and why use it for game state?
Event sourcing stores every change as an immutable event and derives current state by replaying them. It gives a full audit trail, makes it possible to fix bugs by replaying corrected logic, and helps investigate cheating or economy exploits.
How would you shard player data?
Choose a shard key such as player id, hash it to spread players evenly, and keep each player's data on one shard so most queries stay local. Cross-player features like leaderboards need a separate aggregated store.
Where Databases fits in the Server Side Game Developer roadmap
Databases belongs to the Data and Persistence stage (intermediate level), which takes about 4 hours. Never lose a save.
Other units in this stage
Back to the full Server Side Game Developer roadmap