CASE STUDY 04REAL-TIME
TypingWar
Duels where the server keeps score.
ROLEFull-Stack Developer
PERIODJun — Jul 2026
STACK.NET 8 · SignalR Core · Redis
STATUSOpen source · GitHub
04
PROJECT / TYPINGWAR
<30 mslive sync
105+unit tests
THE CONTEXT
Competitive multiplayer typing arena requiring sub-50ms synchronization across duels.
MY ROLE
Architected SignalR duel engine, Redis Pub/Sub sync, and server-side validation.
THE CONSTRAINT
Sub-30ms socket delivery with zero tolerance for spoofed keystrokes or race conditions.
WHAT I BUILT
Three pieces of the puzzle.
01
The battle engine
1v1 live duels, battle rooms, and automated tournament matchmaking on .NET 8.
Duels · rooms · tournaments
02
The real-time layer
SignalR Core and Redis Pub/Sub synchronising keystrokes and WPM under 30ms.
WebSockets · pub/sub · presence
03
The fairness layer
Server-side cadence verification eliminating spoofing, backed by 105+ xUnit tests.
Verification · xUnit · 105+ tests
MEASURED
<30 mslive sync
105+unit tests
1v1duel mode
0trust in the client