I don’t know what I am looking at, but it is fabulous.
That’s the exact comment someone left on a tool called PGSimCity. And it’s the perfect reaction. Because for decades, we’ve been teaching database internals with static architecture diagrams. Arrows. Boxes. Labels. And then we wonder why students’ eyes glaze over.
Static diagrams are the enemy of deep understanding.
You’ve probably sat through a lecture where the professor draws a circular buffer, a few queues, and a scheduler. You nod. You take notes. But do you really see the data moving? The processes competing? The bottlenecks forming? No. You don’t. Because a diagram is a snapshot of a dead system.
PGSimCity turns PostgreSQL’s scheduling into a living, breathing city. Workers are cars. Queues are traffic jams. The buffer is a parking lot. Suddenly, the abstract concepts of process scheduling, I/O wait, and resource contention become visceral. You’re not learning about the scheduler—you’re watching it sweat.
One commenter nailed it: “Understanding how scheduling works inside a database used to require numerous architecture diagrams. I was amazed when I saw PGSimCity — it presents such a complex technical implementation process in such an engaging way.”
This isn’t just a cool toy. It’s a signal. We’re at the edge of a shift in how we teach complex systems. The old way—diagrams, lectures, textbooks—is optimised for explaining. The new way is optimised for experiencing. And experience is what sticks.
When you see a database scheduler as a living city, you never forget how it works.
But here’s the twist: PGSimCity is open-source. That means it’s not a one-off. It’s a blueprint. The same idea—visual, interactive simulation—can be applied to operating systems, networking, even financial markets. The question is: why aren’t we doing this everywhere?
The answer is inertia. We’ve been teaching with diagrams for so long that we’ve mistaken the map for the territory. But the map is flat. The real system is alive. And PGSimCity proves that when you give people a living model, they don’t just learn—they feel the system.
I’ve seen this firsthand. A friend who struggled with database internals for years spent 10 minutes with PGSimCity and said, “Oh. Now I get it.” That’s the power of making the invisible visible.
The best way to learn a complex system is to watch it breathe.
So stop drawing boxes. Start building cities. The future of technical education isn’t prettier diagrams—it’s dynamic, explorable worlds that bridge theory and intuition. And it’s already here.
FAQ
Q: Can a simulation really replace rigorous study of database internals?
A: No, but it builds intuition faster than any static diagram. The simulation gives you a mental model that makes later deep dives stick. You still need to read the docs—but now you'll understand them.
Q: What's the practical implication for someone teaching databases?
A: Stop relying on slide decks of architecture diagrams. Use tools like PGSimCity as a live demo. Let students interact with the simulation before you explain the theory. The 'aha' moments will come naturally.
Q: Isn't this just a gimmick? The real power is still the code, not the visualization.
A: Actually, the real power is that PGSimCity is open-source. You can fork it, tweak it, and build simulations for your own system. The code is the engine of learning, not just the visualization. That's the contrarian truth: the tool itself teaches you how to build such simulations.