🗄️ SQL vs NoSQL Under the Hood
Switch between PostgreSQL, MongoDB and Redis to watch how each engine actually stores and routes a query: a B-tree index walk, sharded document routing, or an O(1) in-memory hash lookup, with replicas and consistency modes you control.
Switch between PostgreSQL, MongoDB and Redis and watch a live query travel through each engine's real storage structure — a B-tree index walk, sharded document routing, or a flat in-memory hash lookup.
🔬 What It Demonstrates
Each engine's architecture is rendered as 3D geometry: PostgreSQL's B-tree index and disk heap, MongoDB's mongos router and shards, and Redis's flat RAM hash grid — with replica nodes syncing behind the primary.
🎮 How to Use
Pick a database engine, then tune query rate, replica count and shard count. Toggle Strong vs Eventual consistency to see replication lag and read latency respond in real time.
💡 Did You Know?
Redis reads are typically sub-millisecond because there is no index tree to walk and no disk seek — the entire dataset already lives in RAM as one big hash table.
Switch between PostgreSQL, MongoDB and Redis to watch how each engine actually stores and routes a query: a B-tree index walk, sharded document routing, or an O(1) in-memory hash lookup, with replicas and consistency modes you control.
3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install