Every Backend Concept Explained for Vibe Coders

You built an app with Lovable, Cursor or Claude Code and it works for 10 people. Here is what happens when 100,000 show up at once. A plain-English system design guide for vibe coders and non-technical founders. 19 software engineering concepts, one concert-ticket app, no code. NOVA TICKETS was built in one evening with AI. Then a famous singer shared it on Instagram and 100,000 fans arrived at 9 AM. The site crashed, logins failed, one fan clicked Pay five times and got charged twice, and the AI assistant replied "The issue has been resolved." It was not. In this video we break that app in every way it can break, then fix it one concept at a time with everyday examples: a supermarket checkout, a hotel reception desk, an elevator button, a café queue, a holiday booking. You will learn rate limiting, caching, load balancing, reverse proxies, API gateways, CI/CD, Docker, Kubernetes, service discovery, circuit breakers, timeouts, retries, exponential backoff, idempotency, message queues, pub/sub, event-driven architecture, distributed transactions and the saga pattern. You do not need all 19 in every app. You need to know which one to ask your AI about when something breaks. Chapters 00:00 Who this video is for 01:08 I built a concert ticket app with AI in one evening 01:43 100,000 fans show up and everything breaks 03:13 What is rate limiting? Stopping 500 refreshes a second 05:10 What is caching? Keeping the menu at the counter 06:59 Load balancing with supermarket checkouts 08:16 What is a reverse proxy? The hotel reception desk 09:24 API gateways and how they differ from a reverse proxy 10:52 What is CI/CD? The pink button that broke checkout 12:32 What is Docker? Fixing "it works on my machine" 13:56 What is Kubernetes, and do you actually need it? 15:19 Service discovery, how services find each other 16:38 Circuit breakers stop one failure from spreading 17:54 Timeouts and why a timeout is not a failed payment 18:47 Retries and why trying again can make things worse 19:50 Exponential backoff and jitter 21:06 Idempotency, or how Rahul gets charged once 23:10 Message queues for emails and background jobs 24:53 Pub/sub explained with YouTube notifications 26:09 Event-driven architecture explained with a wedding 27:38 Distributed transactions, when Rahul pays but gets no ticket 29:14 The saga pattern and compensating actions 30:58 What we actually built 32:44 Do you need all 19 concepts? Probably not 33:32 The real lesson for anyone building with AI Links Connect with me on LinkedIn: [  / anamika-nayak  ] #VibeCoding #SystemDesign #AIAppBuilder