{"id":51066975,"url":"https://github.com/sachinnagesh/system-design-interview-guide","last_synced_at":"2026-06-23T07:30:52.555Z","repository":{"id":357129496,"uuid":"1230150722","full_name":"sachinnagesh/system-design-interview-guide","owner":"sachinnagesh","description":"Created with Claude AI. It's a quick revision guide for system design interview","archived":false,"fork":false,"pushed_at":"2026-05-11T12:03:33.000Z","size":76,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-05-11T14:09:03.941Z","etag":null,"topics":["ai-tools","claude","claude-ai","claude-code","high-level-design","interview","interview-preparation","javascript","js","low-level-design","system-design","system-design-interview"],"latest_commit_sha":null,"homepage":"https://system-design-interview-guide.vercel.app/","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/sachinnagesh.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-05-05T18:17:51.000Z","updated_at":"2026-05-11T12:06:21.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/sachinnagesh/system-design-interview-guide","commit_stats":null,"previous_names":["sachinnagesh/system-design-interview-guide"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/sachinnagesh/system-design-interview-guide","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sachinnagesh%2Fsystem-design-interview-guide","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sachinnagesh%2Fsystem-design-interview-guide/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sachinnagesh%2Fsystem-design-interview-guide/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sachinnagesh%2Fsystem-design-interview-guide/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/sachinnagesh","download_url":"https://codeload.github.com/sachinnagesh/system-design-interview-guide/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sachinnagesh%2Fsystem-design-interview-guide/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34680620,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-23T02:00:07.161Z","response_time":65,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-tools","claude","claude-ai","claude-code","high-level-design","interview","interview-preparation","javascript","js","low-level-design","system-design","system-design-interview"],"created_at":"2026-06-23T07:30:50.744Z","updated_at":"2026-06-23T07:30:52.549Z","avatar_url":"https://github.com/sachinnagesh.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# System Design Interview Guide — HLD + LLD\n\nA free, interactive study guide for system design interviews. Covers both **High-Level Design** and **Low-Level Design** with real-world case studies, trade-off analysis, and a structured interview framework.\n\n**Live site →** [system-design-interview-guide.vercel.app](https://system-design-interview-guide.vercel.app)\n\n---\n\n## What's Inside\n\n**15 topics · 80+ concepts · 40+ case studies · Every concept with trade-offs**\n\n### High-Level Design (8 topics)\n\n| Topic | Concepts | Case Studies |\n|-------|----------|-------------|\n| ⚡ **Scalability** | Vertical vs Horizontal Scaling, Load Balancers, Stateless Architecture, Auto-scaling | Netflix (200M+ subs), Twitter/X (election surges) |\n| 🗄️ **Databases** | SQL vs NoSQL, Sharding, Replication, Indexing, Partitioning | Instagram (sharding), Discord (Cassandra migration), Uber (polyglot persistence) |\n| ⚡💾 **Caching** | Cache-Aside, Write-Through, Write-Behind, Eviction Policies, Redis vs Memcached | Facebook TAO, Twitter timeline fan-out, Stack Overflow multi-layer cache |\n| 📨 **Message Queues** | Kafka, RabbitMQ/SQS, Pub/Sub, At-Least-Once vs Exactly-Once, Back-pressure | LinkedIn (Kafka origin story), Uber (async dispatch), DoorDash (order pipeline) |\n| 🌐 **CDN \u0026 Networking** | CDN, DNS, TCP vs UDP, HTTP vs WebSockets vs SSE, Edge Computing | Netflix Open Connect, Discord WebSockets, Cloudflare anycast DDoS |\n| ⚖️ **CAP \u0026 Consistency** | CAP Theorem, Strong vs Eventual Consistency, ACID, BASE, Isolation Levels | Amazon DynamoDB (AP), Banking systems (CP), Google Spanner (TrueTime) |\n| 🔧 **Microservices** | Monolith vs Microservices, API Gateway, Service Discovery, Circuit Breaker, Saga Pattern | Amazon (two-pizza teams), Netflix Hystrix, Spotify squads |\n| 🚦 **Rate Limiting** | Token Bucket, Leaky Bucket, Fixed Window, Sliding Window, Distributed Rate Limiting | GitHub API limits, Stripe fraud prevention, Cloudflare edge limiting |\n\n### Low-Level Design (6 topics)\n\n| Topic | Concepts | Case Studies |\n|-------|----------|-------------|\n| 🎯 **OOP Principles** | Encapsulation, Inheritance, Polymorphism, Abstraction, Composition over Inheritance | Java Collections Framework, Stripe payment processor |\n| 📐 **SOLID Principles** | Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion | Spring Framework DI, AWS SDK design |\n| 🏗️ **Design Patterns** | Singleton, Factory, Observer, Strategy, Decorator, Builder | React state (Observer), Java I/O (Decorator), Spring (combined patterns) |\n| 🔄 **Concurrency** | Threads vs Processes, Locks/Mutex/Semaphore, Deadlock, Async/Await, Producer-Consumer | Node.js event loop, Java ConcurrentHashMap, Go goroutines |\n| 🔌 **API Design** | REST, GraphQL, gRPC, Idempotency, Versioning, Pagination | Stripe idempotency keys, GitHub cursor pagination, Facebook GraphQL |\n| 📊 **Schema \u0026 Modeling** | Normalization, Denormalization, Indexing Strategy, Soft Deletes, Embedding vs Referencing | Instagram feed denormalization, Shopify multi-tenant, Airbnb soft deletes |\n\n### Interview Framework (1 topic)\n\nA structured 5-step approach to answering any system design question — clarify requirements, capacity estimation, high-level design, deep dive, bottlenecks — with complete FAANG walkthrough examples.\n\n---\n\n## Features\n\n- **Trade-off panels** for every concept (Pros / Cons / When to use)\n- **Real case studies** from Netflix, Uber, Discord, Instagram, Stripe, Amazon, Google, and more\n- **Interview tips** with exact talking points for each topic\n- **Category filters** (HLD / LLD / Framework) for focused studying\n- **Responsive design** — works on desktop, tablet, and mobile\n- **Dark theme** optimized for reading\n- **Zero external dependencies** — just React and Next.js\n- **No tracking, no ads, no data collection**\n\n---\n\n## Getting Started\n\n### Prerequisites\n\n- [Node.js](https://nodejs.org/) 18 or higher\n\n### Run Locally\n\n```bash\ngit clone https://github.com/sachinnagesh/system-design-interview-guide.git\ncd system-design-interview-guide\nnpm install\nnpm run dev\n```\n\nOpen [http://localhost:3000](http://localhost:3000).\n\n### Build for Production\n\n```bash\nnpm run build\nnpm start\n```\n\n---\n\n## Deploy\n\n### Vercel (Recommended)\n\n[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/YOUR_USERNAME/system-design-interview-guide)\n\nOr manually:\n\n1. Push this repo to GitHub\n2. Go to [vercel.com/new](https://vercel.com/new)\n3. Import the repository\n4. Click Deploy\n\n### Other Platforms\n\nWorks on **Netlify**, **Cloudflare Pages**, **Railway**, **Docker**, or any Node.js host. See [Next.js deployment docs](https://nextjs.org/docs/deployment) for details.\n\n---\n\n## Project Structure\n\n```\n├── app/\n│   ├── layout.jsx              # Root layout, metadata, SEO\n│   └── page.jsx                # Home page\n├── components/\n│   └── SystemDesignGuide.jsx   # Main component (all content + UI)\n├── public/\n│   ├── robots.txt              # Search engine crawling\n│   └── sitemap.xml             # Search engine indexing\n├── package.json\n├── next.config.js\n├── jsconfig.json\n└── README.md\n```\n\nAll content lives in `components/SystemDesignGuide.jsx` inside the `topics` array. Each topic follows this structure:\n\n```javascript\n{\n  id: \"scalability\",\n  category: \"HLD\",            // HLD | LLD | FRAMEWORK\n  icon: \"⚡\",\n  title: \"Scalability\",\n  color: \"#00D4FF\",\n  tagline: \"Handle more load without breaking\",\n  simple: \"ELI5 explanation...\",\n  concepts: [\n    {\n      name: \"Horizontal Scaling\",\n      desc: \"Description...\",\n      tradeoffs: {\n        pros: [\"...\"],\n        cons: [\"...\"]\n      },\n      when: \"When to use...\",\n      interview: \"What to say in an interview...\"\n    }\n  ],\n  use_cases: [\n    {\n      company: \"Netflix\",\n      title: \"Handling 200M+ subscribers\",\n      problem: \"...\",\n      solution: \"...\",\n      tradeoff: \"...\",\n      takeaway: \"...\"\n    }\n  ],\n  interview_tips: [\"...\", \"...\"]\n}\n```\n\n---\n\n## Contributing\n\nContributions are welcome. You can:\n\n- **Add a topic** — add a new object to the `topics` array\n- **Add concepts** — expand the `concepts` array within a topic\n- **Add case studies** — add to the `use_cases` array\n- **Fix errors** — correct any inaccuracies in explanations\n- **Improve UI** — enhance the responsive design or interactions\n\n### How to Contribute\n\n1. Fork this repository\n2. Create a branch: `git checkout -b add-new-topic`\n3. Make your changes in `components/SystemDesignGuide.jsx`\n4. Test locally: `npm run dev`\n5. Submit a pull request\n\nPlease keep the same content structure and tone. Every concept should include trade-offs (pros/cons), a \"when to use\" section, and an interview tip.\n\n---\n\n## Study Plan\n\nA suggested 4-week preparation schedule:\n\n**Week 1 — HLD Foundations**\n- Day 1–2: Scalability, Databases\n- Day 3–4: Caching, Message Queues\n- Day 5–6: CDN \u0026 Networking, CAP \u0026 Consistency\n- Day 7: Microservices, Rate Limiting\n\n**Week 2 — LLD Foundations**\n- Day 1–2: OOP Principles, SOLID\n- Day 3–4: Design Patterns, Concurrency\n- Day 5–6: API Design, Schema \u0026 Modeling\n- Day 7: Review all LLD topics\n\n**Week 3 — Deep Dive \u0026 Case Studies**\n- Read every case study across all topics\n- Practice explaining trade-offs aloud\n- Draw architecture diagrams on paper/whiteboard\n\n**Week 4 — Mock Interviews**\n- Use the Interview Framework topic as your template\n- Practice 2 full mock interviews per day\n- Review weak areas using the guide\n\n---\n\n## Tech Stack\n\n- **Framework:** [Next.js](https://nextjs.org/) 14\n- **UI:** [React](https://react.dev/) 18\n- **Styling:** Inline CSS (zero dependencies)\n- **Fonts:** Google Fonts (Playfair Display, DM Sans, DM Mono)\n- **Hosting:** [Vercel](https://vercel.com/)\n\n---\n\n## License\n\nMIT — free to use, modify, and distribute.\n\n---\n\n## Acknowledgments\n\nContent is synthesized from publicly available engineering blogs, conference talks, and documentation from companies including Netflix, Uber, Discord, Instagram, Stripe, Amazon, Google, Facebook, LinkedIn, Spotify, Cloudflare, DoorDash, Shopify, and Airbnb.\n\n---\n\n**If this helped you prepare for interviews, consider giving it a ⭐ on GitHub.**","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsachinnagesh%2Fsystem-design-interview-guide","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsachinnagesh%2Fsystem-design-interview-guide","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsachinnagesh%2Fsystem-design-interview-guide/lists"}