Compare Scenarios

Migration Step 1

Both scenarios define a migration step at this stage. Gaming Backend Platform: triggered by 'Single game server instance running at connection ceiling; h'. Write-Heavy Transactional Platform: triggered by 'Dual-write inconsistency events observed in production: DB w'.

Migration Step 2

Both scenarios define a migration step at this stage. Gaming Backend Platform: triggered by 'Game server instances blocking on PostgreSQL writes at end-o'. Write-Heavy Transactional Platform: triggered by 'Primary write CPU > 70% sustained during peak windows; WAL v'.

Migration Step 3

Both scenarios define a migration step at this stage. Gaming Backend Platform: triggered by 'PostgreSQL event log table approaching 100B rows; reconnect '. Write-Heavy Transactional Platform: triggered by 'Audit completeness requirements grow beyond point-in-time ba'.

Game server instance file descriptor count approaching OS limit (typically 65k open connections); WebSocket accept latency increasing; new connection establishment p99 > 200ms; CPU on game server instances > 70% during peak concurrent player count

Tier 1: WebSocket Connection Ceiling per Instance: Single game server instance WebSocket connection count limit; OS-level fd_max or application-level connection accept queue saturation. Recommended evolution: Increase OS fd_max to 512k and application connection accept queue depth; tune SO_REUSEPORT to allow multiple accept threads per socket; add game server instances and update consistent hashing ring; the affinity layer automatically routes new game rooms to the new instances as the ring expands: existing rooms are unaffected .

Redis command throughput > 500k/second; Redis CPU > 60%; per-tick Redis write latency p99 > 5ms (above the acceptable state sync threshold); game tick rate visibly dropping below target (30 ticks/second falling to 20) under load

Tier 2: Redis Game State Write Amplification: Game state serialization to Redis per tick producing more writes than expected; unoptimized state struct serialization writing entire state blob on any field change. Recommended evolution: Implement delta state serialization: only changed fields are written to Redis per tick using HSET with only the modified keys, not full state replacement; profile Redis command distribution per game tick to identify specific state fields with high churn; consider moving ephemeral per-tick state (player positions, projectile states) to local server memory with only durable state (scores, inventory changes) written to Redis .

PgBouncer wait_queue > 0 sustained; application p99 write latency rising faster than PostgreSQL p99; pool_mode=transaction showing >80% utilization

Tier 1: Connection Pool Saturation: PgBouncer pool_size too small for write concurrency profile. Recommended evolution: Increase PgBouncer pool_size incrementally; profile transaction duration to right-size pool; consider separate pools for write-heavy and read-only workloads .

PostgreSQL checkpoint_completion_target warnings in logs; wal_buffers flushing more than once per second; pg_stat_bgwriter shows checkpoints_req rising; write p99 > 20ms without query explanation

Tier 2: WAL and Checkpoint Pressure: Write rate exceeding PostgreSQL's WAL flush and checkpoint throughput. Recommended evolution: Tune checkpoint_completion_target to 0.9; increase wal_buffers to 64MB; move PostgreSQL WAL to a dedicated NVMe volume separate from data directory .