Wink Pings

System design shouldn't be just for interviews: someone turned it into a 40-lesson course you can click through

Dilum Sanjaya breaks system design into 40 interactive lessons. You can click through step by step to see how a request travels through DNS, connections, servers, and databases. For people who rely on AI to write code, this feels more like filling in an architecture course they skipped.

Dilum Sanjaya posted a web app on X called Designed to Scale. The address is https://designed-to-scale.vercel.app . The problem it aims to solve isn't complicated: system design shouldn't exist only in interview trivia and whiteboard diagrams. It has 40 lessons across 9 modules, from the request lifecycle, latency and throughput, and estimation, to caching, sharding, consistency, message queues, rate limiting, and observability, then on to complete system designs such as a URL shortener, news feed, and chat system.

The author puts it bluntly in the tweet: understanding system design helps you build better apps, even if you're vibe coding. Better architecture decisions, better AI prompts, fewer surprises as the app grows. That sentence is worth pausing on. AI can write the code, but where to put the cache, how to shard data, how to retry failures, and when to split services—none of these automatically get answered just because generation gets faster.

The first lesson is called How a Request Travels, is 10 minutes long, and has 10 steps. It follows a single page load: you type shop.example, press Enter, and about a sixth of a second later the page appears. In between, a DNS lookup happens, a connection is established, the request hits the server, the server queries the database, and files download. The app turns these steps into a playable animation, with the time for each step labeled alongside it. It doesn't start with the CAP theorem or throw a microservices architecture diagram at you first; it first lets you see clearly where the time actually goes. That ordering is smarter than many system design courses.

In the course catalog you can see the specific topics: Vertical vs Horizontal, Load Balancing, Caching, SQL vs NoSQL, Indexes, Replication, Sharding, CAP & Consistency, Message Queues, Rate Limiting, Monolith vs Microservices, Sagas & Distributed Tx, Authentication, CI/CD & Deployments. The complete systems section includes Design a URL Shortener, Design a News Feed, and Design a Chat System. For readers without a development background, these terms don't need to be memorized all at once. Its value lies in breaking abstract processes into steps you can click through, so how a request travels first becomes something you can picture.

In a reply, the author mentions that he plans to make another app covering MCP and other AI-related architecture concepts. That direction isn't surprising. The faster agents write code, the more people need to know how systems fit together. One commenter puts it even more bluntly: agents can quickly give you working code, but they can't give you the diagram of how these things hang together. Another says system design is the IKEA instruction manual that vibe coders throw away. It's a bit harsh, but not far off.

Designed to Scale is only one of them. Protocol Explorer turns internet protocols into a visual quick reference, with a packet inspector. The tweet says it covers 14 internet protocols, while the page already lists 39 protocol entries, from HTTP, HTTPS, WebSocket, and WebRTC to TCP, UDP, BGP, DNS, TLS, SSH, and WireGuard. Each protocol is broken into several steps, such as TCP's three-way handshake, retransmission after packet loss, and connection teardown. The address is https://protocol-explorer-alpha.vercel.app .

He has also made Learn Arduino, Learn ESP32, Electronics 101, RoverKit, and Backcountry 101. RoverKit supports Arduino and ESP32, and includes a simulator, customizable arenas, and a visual code flow. One commenter asks whether the simulator models ultrasonic anomalies on slopes, and another says the simulator lacks real friction. These criticisms aren't unreasonable. Visual learning can lower the barrier to entry, but it can't replace a soldering station, jumper wires, and debugging. In a reply, Dilum Sanjaya says RoverKit started as an experiment to test Fable designing a robot, and later became a tutorial. That sequence is realistic too: first make something that runs, then turn it into a course.

If you have a development background, Designed to Scale works well as a system design review map. If you don't have a technical background, the first lesson is friendly enough: it only asks that you know what happens after you type a URL into a browser. You can click through the rest slowly. System design isn't only for the run-up to interviews. When an app grows up, it will come back to find you.

发布时间: 2026-11-17 08:32