261 lines
12 KiB
Markdown
261 lines
12 KiB
Markdown
# The System Design Primer
|
|
|
|
<p align="center">
|
|
<img src="http://i.imgur.com/jrUBAF7.png">
|
|
<br/>
|
|
</p>
|
|
|
|
## Motivation
|
|
|
|
> Learn how to design large scale systems from the open source community.
|
|
>
|
|
> Understand real-world architectures.
|
|
>
|
|
> Prep for the system design interview.
|
|
|
|
### Learn how to design large scale systems
|
|
|
|
Learning how to design scalable systems will make you a better engineer.
|
|
|
|
System design is a broad topic. There is a **vast amount of resources scattered throughout the web** on system design principles.
|
|
|
|
This repo is an **organized collection** of resources to help you learn how to build systems at scale.
|
|
|
|
Topics for learning system design:
|
|
|
|
* [System design topic summaries](#index-of-system-design-topics)
|
|
* [Real world architectures](#real-world-architectures)
|
|
* [Engineering blogs](#company-engineering-blogs)
|
|
|
|
#### Learn from the open source community
|
|
|
|
This is an **early draft** of a **continually updated, open source** project.
|
|
|
|
[Contributions](#contributin) are welcome!
|
|
|
|
### Prep for the system design interview
|
|
|
|
In addition to coding interviews, system design is a **required component** of the **technical interview process** at many tech companies.
|
|
|
|
**Practice common system design interview questions** and **compare** your results with sample **discussions, code, and diagrams**.
|
|
|
|
Additional topics for interview prep:
|
|
|
|
* [Study guide](#study-guide)
|
|
* [How to approach a system design interview question](#how-to-approach-a-system-design-interview-question)
|
|
* [System design interview questions, **with solutions**](#system-design-interview-questions-with-solutions)
|
|
* [Object-oriented design interview questions, **with solutions**](#object-oriented-design-interview-questions-with-solutions)
|
|
* [Additional system design interview questions](#additional-system-design-interview-questions)
|
|
|
|
#### For interviews, do I need to know everything here?
|
|
|
|
**No, you don't need to know everything here to prepare for the interview**.
|
|
|
|
What you are asked in an interview depends on variables such as:
|
|
|
|
* How much experience you have
|
|
* What your technical background is
|
|
* What positions you are interviewing for
|
|
* Which companies you are interviewing with
|
|
* Luck
|
|
|
|
More experienced candidates are generally expected to know more about system design. Architects or team leads might be expected to know more than individual contributors. Top tech companies are likely to have one or more design interview rounds.
|
|
|
|
#### Any resources to prep for coding interviews?
|
|
|
|
Check out the sister repo [**interactive-coding-challenges**](https://github.com/donnemartin/interactive-coding-challenges) for coding interview resources.
|
|
|
|
## Contributing
|
|
|
|
> Learn from the community.
|
|
|
|
Feel free to submit pull requests to help:
|
|
|
|
* Fix errors
|
|
* Improve sections
|
|
* Add new sections
|
|
|
|
Content that needs some polishing is placed [under development](#under-development).
|
|
|
|
Review the [Contributing Guidelines](https://github.com/donnemartin/awesome-aws/blob/master/CONTRIBUTING.md).
|
|
|
|
## Index of system design topics
|
|
|
|
> Summaries of various system design topics, including pros and cons. **Everything is a trade-off**.
|
|
>
|
|
> Each section contains links to more in-depth resources.
|
|
|
|
|
|
|
|
* [System design topics: start here](#system-design-topics-start-here)
|
|
* [Step 1: Review the scalability video lecture](#step-1-review-the-scalability-video-lecture)
|
|
* [Step 2: Review the scalability article](#step-2-review-the-scalability-article)
|
|
* [Next steps](#next-steps)
|
|
* [Performance vs scalability](#performance-vs-scalability)
|
|
* [Latency vs throughput](#latency-vs-throughput)
|
|
* [Availability vs consistency](#availability-vs-consistency)
|
|
* [CAP theorem](#cap-theorem)
|
|
* [CP - consistency and partition tolerance](#cp-consistency-and-partition-tolerance)
|
|
* [AP - availability and partition tolerance](#ap-availability-and-partition-tolerance)
|
|
* [Consistency patterns](#consistency-patterns)
|
|
* [Weak consistency](#weak-consistency)
|
|
* [Eventual consistency](#eventual-consistency)
|
|
* [Strong consistency](#strong-consistency)
|
|
* [Availability patterns](#availability-patterns)
|
|
* [Fail-over](#fail-over)
|
|
* [Replication](#replication)
|
|
* [Domain name system](#domain-name-system)
|
|
* [Content delivery network](#content-delivery-network)
|
|
* [Push CDNs](#push-cdns)
|
|
* [Pull CDNs](#pull-cdns)
|
|
* [Load balancer](#load-balancer)
|
|
* [Active-passive](#active-passive)
|
|
* [Active-active](#active-active)
|
|
* [Layer 4 load balancing](#layer-4-load-balancing)
|
|
* [Layer 7 load balancing](#layer-7-load-balancing)
|
|
* [Horizontal scaling](#horizontal-scaling)
|
|
* [Reverse proxy (web server)](#reverse-proxy-web-server)
|
|
* [Load balancer vs reverse proxy](#load-balancer-vs-reverse-proxy)
|
|
* [Application layer](#application-layer)
|
|
* [Microservices](#microservices)
|
|
* [Service discovery](#service-discovery)
|
|
* [Database](#database)
|
|
* [SQL](#sql)
|
|
* [Relational database management system (RDBMS)](relational-database-management-system-rdbms)
|
|
* [Scaling SQL](#scaling-sql)
|
|
* [Master-slave replication](#master-slave-replication)
|
|
* [Federation](#federation)
|
|
* [Sharding](#sharding)
|
|
* [Denormalization](#denormalization)
|
|
* [SQL tuning](#sql-tuning)
|
|
* [NoSQL](#nosql)
|
|
* [Key-value store](#key-value-store)
|
|
* [Document store](#document-store)
|
|
* [Wide column store](#wide-column-store)
|
|
* [Graph Database](#graph-database)
|
|
* [SQL or NoSQL](#sql-or-nosql)
|
|
* [Cache](#cache)
|
|
* [Client caching](#client-caching)
|
|
* [CDN caching](#cdn-caching)
|
|
* [Web server caching](#web-server-caching)
|
|
* [Database caching](#database-caching)
|
|
* [Application caching](#application-caching)
|
|
* [Caching at the database query level](#caching-at-the-database-query-level)
|
|
* [Caching at the object level](#caching-at-the-object-level)
|
|
* [When to update the cache](#when-to-update-the-cache)
|
|
* [Cache-aside](#cache-aside)
|
|
* [Write-through](#write-through)
|
|
* [Write-behind (write-back)](#write-behind-write-back)
|
|
* [Refresh-ahead](#refresh-ahead)
|
|
* [Asynchronism](#asynchronism)
|
|
* [Message queues](#message-queues)
|
|
* [Task queues](#task-queues)
|
|
* [Back pressure](#back-pressure)
|
|
* [Communication](#communication)
|
|
* [Transmission control protocol (TCP)](#transmission-control-protocol-tcp)
|
|
* [User datagram protocol (UDP)](#user-datagram-protocol-udp)
|
|
* [Remote procedure call (RPC)](#remote-procedure-call-rpc)
|
|
* [Representational state transfer (REST)](#representational-state-transfer-rest)
|
|
* [Security](#security)
|
|
* [Appendix](#appendix)
|
|
* [Powers of two table](#powers-of-two-table)
|
|
* [Latency numbers every programmer should know](#latency-numbers-every-programmer-should-know)
|
|
* [Under development](#under-development)
|
|
* [Distributed computing](#distributed-computing)
|
|
* [Consistent hashing](#consistent-hashing)
|
|
* [Scatter gather](#scatter-gather)
|
|
* [Contribute](#contributing)
|
|
* [Credits](#credits)
|
|
* [Contact info](#contact-info)
|
|
* [License](#license)
|
|
|
|
## Study guide
|
|
|
|
> Suggested topics to review based on your interview timeline (short, medium, long).
|
|
|
|
|
|
|
|
Start broad and go deeper in a few areas. It helps to know a little about various key system design topics. Adjust the following guide based on your experience, what positions you are interviewing for, and which companies you are interviewing with.
|
|
|
|
* **Short** - Aim for **breadth** with system design topics. Practice by solving **some** interview questions.
|
|
* **Medium** - Aim for **breadth** and **some depth** with system design topics. Practice by solving a **many** interview questions.
|
|
* **Long** - Aim for **breadth** and **more depth** with system design topics. Practice by solving a **most** interview questions.
|
|
|
|
| | Short | Medium | Long |
|
|
|---|---|---|---|
|
|
| Read through the [System design topics](#index-of-system-design-topics) to get a broad understanding of how systems work | :+1: | :+1: | :+1: |
|
|
| Read through a few articles in the [Company engineering blogs](#company-engineering-blogs) for the companies you are interviewing with | :+1: | :+1: | :+1: |
|
|
| Read through a few [Real world architectures](#real-world-architectures) | :+1: | :+1: | :+1: |
|
|
| Review [How to approach a system design interview question](#how-to-approach-a-system-design-interview-question) | :+1: | :+1: | :+1: |
|
|
| Work through [System design interview questions with solutions](#system-design-interview-questions-with-solutions) | Some | Many | Most |
|
|
| Work through [Object-oriented design interview questions with solutions](#object-oriented-design-interview-questions-with-solutions) | Some | Many | Most |
|
|
| Review [Additional system design interview questions](#additional-system-design-interview-questions) | Some | Many | Most |
|
|
|
|
## How to approach a system design interview question
|
|
|
|
> How to tackle a system design interview question.
|
|
|
|
The system design interview is an **open-ended conversation**. You are expected to lead it.
|
|
|
|
You can use the following steps to guide the discussion. To help solidify this process, work through the [System design interview questions with solutions](#system-design-interview-questions-with-solutions) section using the following steps.
|
|
|
|
### Step 1: Outline use cases, constraints, and assumptions
|
|
|
|
Gather requirements and scope the problem. Ask questions to clarify use cases and constraints. Discuss assumptions.
|
|
|
|
* Who is going to use it?
|
|
* How are they going to use it?
|
|
* How many users are there?
|
|
* What does the system do?
|
|
* What are the inputs and outputs of the system?
|
|
* How much data do we expect to handle?
|
|
* How many requests per second do we expect?
|
|
* What is the expected read to write ratio?
|
|
|
|
### Step 2: Create a high level design
|
|
|
|
Outline a high level design with all important components.
|
|
|
|
* Sketch the main components and connections
|
|
* Justify your ideas
|
|
|
|
### Step 3: Design core components
|
|
|
|
Dive into details for each core component. For example, if you were asked to [design a url shortening service](https://github.com/donnemartin/system-design/blob/master/solutions/system_design/pastebin/README.md), discuss:
|
|
|
|
* Generating and storing a hash of the full url
|
|
* [MD5](https://github.com/donnemartin/system-design/blob/master/solutions/system_design/pastebin/README.md) and [Base62](https://github.com/donnemartin/system-design/blob/master/solutions/system_design/pastebin/README.md)
|
|
* Hash collisions
|
|
* SQL or NoSQL
|
|
* Database schema
|
|
* Translating a hashed url to the full url
|
|
* Database lookup
|
|
* API and object-oriented design
|
|
|
|
### Step 4: Scale the design
|
|
|
|
Identify and address bottlenecks, given the constraints. For example, do you need the following to address scalability issues?
|
|
|
|
* Load balancer
|
|
* Horizontal scaling
|
|
* Caching
|
|
* Database sharding
|
|
|
|
Discuss potential solutions and trade-offs. Everything is a trade-off. Address bottlenecks using [principles of scalable system design](#index-of-system-design-topics).
|
|
|
|
### Back-of-the-envelope calculations
|
|
|
|
You might be asked to do some estimates by hand. Refer to the [Appendix](#appendix) for the following resources:
|
|
|
|
* [Use back of the envelope calculations](http://highscalability.com/blog/2011/1/26/google-pro-tip-use-back-of-the-envelope-calculations-to-choo.html)
|
|
* [Powers of two table](#powers-of-two-table)
|
|
* [Latency numbers every programmer should know](#latency-numbers-every-programmer-should-know)
|
|
|
|
### Source(s) and further reading
|
|
|
|
Check out the following links to get a better idea of what to expect:
|
|
|
|
* [How to ace a systems design interview](https://www.palantir.com/2011/10/how-to-rock-a-systems-design-interview/)
|
|
* [The system design interview](http://www.hiredintech.com/system-design)
|
|
* [Intro to Architecture and Systems Design Interviews](https://www.youtube.com/watch?v=ZgdS0EUmn70)
|