> For the complete documentation index, see [llms.txt](https://www.opscompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opscompendium.com/architecture/system-design.md).

# System Design

1. (Amazing)[ System Design in a Hurry](https://www.hellointerview.com/learn/system-design/in-a-hurry/introduction)
2. (Amazing) [**System Design and architecture**](https://github.com/puncsky/system-design-and-architecture)\\

   ![Puncsky](https://lh4.googleusercontent.com/UpUWT6Jx5fE_l9YMZQuCa4c_-OlpXYYZldQzF3l1A2H-B2Sd8uMQAdekbeeIXNdKdooKShlFSN6bncvUjvOUB3F7-_drbrFx9ZO6kQ4rrcRoWqyNJjZ33X_3ewgs0leEndte3Xhw)
3. [Hired in tech](https://www.hiredintech.com/system-design/) - high level
4. [Episode 06: Intro to Architecture and Systems Design Interviews](https://www.youtube.com/watch?v=ZgdS0EUmn70) - an approach
5. [System design template](https://leetcode.com/discuss/career/229177/My-System-Design-Template)
6. [RAG SD](https://blogs.nvidia.com/blog/what-is-retrieval-augmented-generation/)
7. Jordan
   1. [Distributed Job Scheduler](https://www.youtube.com/watch?v=pzDwYHRzEnk)
   2. [Distributed Locking](https://www.youtube.com/watch?v=Lp8oITg0MiI)
   3. [Rate Limiter](https://www.youtube.com/watch?v=VzW41m4USGs)
8. [(great) System Design Primer](https://github.com/donnemartin/system-design-primer/tree/master) -Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.
9. [CS75 (Summer 2012) Lecture 9 Scalability Harvard Web Development David Malan](https://www.youtube.com/watch?v=-W9F__D3oY4)
10. Scalability
    1. [a word about](https://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html)
    2. [scalability for dummies](https://web.archive.org/web/20221030091841/http://www.lecloud.net/tagged/scalability/chrono) [1](https://web.archive.org/web/20220530193911/https://www.lecloud.net/post/7295452622/scalability-for-dummies-part-1-clones) [2](https://web.archive.org/web/20220602114024/https://www.lecloud.net/post/7994751381/scalability-for-dummies-part-2-database) [3](https://web.archive.org/web/20230126233752/https://www.lecloud.net/post/9246290032/scalability-for-dummies-part-3-cache) [4](https://web.archive.org/web/20220926171507/https://www.lecloud.net/post/9699762917/scalability-for-dummies-part-4-asynchronism)
    3. (good for topics) [Scalability, Availability & Stability Patterns](https://www.slideshare.net/slideshow/scalability-availability-stability-patterns/4062682)
    4. (good) [Use Back-of-the-envelope-calculations to Choose the Best Design](https://highscalability.com/google-pro-tip-use-back-of-the-envelope-calculations-to-choo/)
11. [System Design Guided Practice](https://bugfree.ai/) - AI-Powered platform provided guided practice on system design problem and behavior questions like the way you do at Leetcode.
12. [PracHub System Design Practice](https://prachub.com/categories/system-design) - Company-tagged interview prompts for timed, answer-first practice.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opscompendium.com/architecture/system-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
