I'll be upfront: I'm writing this after trying most of the "big name" system design resources first-the video courses, the diagram-heavy blogs, the flashcard decks. Not because they're bad, but because none of them actually made me better at designing systems. They made me better at recognizing good designs when I saw them, which is a completely different skill.
Here's why ScaleDojo ended up being the one that actually moved the needle for me.
The problem every other resource has in common
You can watch fifty hours of system design videos and still freeze the moment someone asks you to build something from scratch. This isn't a knowledge gap-it's a practice gap. Watching someone else design a system trains pattern recognition. It does not train the muscle of actually producing an architecture yourself, under a little pressure, with someone asking follow-up questions.
Almost every popular system design resource is built around reading or watching. ScaleDojo is the first one I used that's built around building.
What it actually is
ScaleDojo is a hands-on system design practice platform-think of it less like a course and more like the LeetCode of system design. Instead of reading about how to design a rate limiter, you're on an interactive canvas actually dragging in load balancers, connecting services, and wiring up the data flow yourself.
It's organized into a few focused labs:
HLD Architecture Lab — the classic big-picture stuff: load balancers, caching, message queues, service boundaries
LLD Schema Design Lab — database schema design on an actual ER canvas, not a diagram you're just supposed to memorize
API Design Lab — REST endpoint design, pagination, error handling-the part almost every other resource skips entirely
GenAI Systems Lab — RAG pipelines, vector databases, AI agent architecture, which is genuinely the newest and most underserved part of system design prep right now
The part that actually changed how I practice
Every submission gets scored, and then reviewed by an AI Architect that tells you specifically what you got right, what you missed, and what a senior engineer would have done differently. That loop-build, get specific feedback, fix it, build again-is the entire thing that was missing from every book and video course I'd used before.
It's not asking "is your diagram correct." It's asking does this actually hold up,and telling you exactly where it doesn't.
Who this is actually for
If you already understand the concepts-you know what a load balancer does, you've heard of consistent hashing-but freeze when asked to apply any of it live, this is built for exactly that gap. It's less useful if you're a complete beginner with zero foundation; pair it with a good book or video series first to build the mental models, then come here to turn that understanding into an actual skill.
The honest bottom line
I'm not saying skip everything else. Read the books, watch the videos that explain the internals well-that part still matters. But at some point you have to stop reading about system design and start actually doing it, with something in front of you that tells you when you're wrong and why. That's the gap ScaleDojo closed for me, and it's why it's the one resource out of everything I tried that I'd actually recommend first.
Top comments (4)
Nice..
agreed!!
good curated content❤️
Worth reading!