mirror of
https://github.com/donnemartin/system-design-primer.git
synced 2025-10-17 17:22:53 +03:00
Add pandoc for PDF creation and GitHub Actions for auto-generation
This commit is contained in:
@@ -80,7 +80,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -327,7 +327,7 @@ class SpendingByCategory(MRJob):
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -79,7 +79,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -235,7 +235,7 @@ To delete expired pastes, we could just scan the **SQL Database** for all entrie
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -58,7 +58,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -212,7 +212,7 @@ Refer to [When to update the cache](https://github.com/donnemartin/system-design
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -70,7 +70,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -239,7 +239,7 @@ For internal communications, we could use [Remote Procedure Calls](https://githu
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -64,7 +64,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -139,7 +139,7 @@ Add a **DNS** such as Route 53 to map the domain to the instance's public IP.
|
||||
|
||||
### Users+
|
||||
|
||||

|
||||

|
||||
|
||||
#### Assumptions
|
||||
|
||||
@@ -191,7 +191,7 @@ We've been able to address these issues with **Vertical Scaling** so far. Unfor
|
||||
|
||||
### Users++
|
||||
|
||||

|
||||

|
||||
|
||||
#### Assumptions
|
||||
|
||||
@@ -220,7 +220,7 @@ Our **Benchmarks/Load Tests** and **Profiling** show that our single **Web Serve
|
||||
|
||||
### Users+++
|
||||
|
||||

|
||||

|
||||
|
||||
**Note:** **Internal Load Balancers** not shown to reduce clutter
|
||||
|
||||
@@ -258,7 +258,7 @@ Our **Benchmarks/Load Tests** and **Profiling** show that we are read-heavy (100
|
||||
|
||||
### Users++++
|
||||
|
||||

|
||||

|
||||
|
||||
#### Assumptions
|
||||
|
||||
@@ -297,7 +297,7 @@ Our **Benchmarks/Load Tests** and **Profiling** show that our traffic spikes dur
|
||||
|
||||
### Users+++++
|
||||
|
||||

|
||||

|
||||
|
||||
**Note:** **Autoscaling** groups not shown to reduce clutter
|
||||
|
||||
|
@@ -50,7 +50,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -250,7 +250,7 @@ For internal communications, we could use [Remote Procedure Calls](https://githu
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -93,7 +93,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -223,7 +223,7 @@ The response would be similar to that of the home timeline, except for tweets ma
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
@@ -69,7 +69,7 @@ Handy conversion guide:
|
||||
|
||||
> Outline a high level design with all important components.
|
||||
|
||||

|
||||

|
||||
|
||||
## Step 3: Design core components
|
||||
|
||||
@@ -256,7 +256,7 @@ For internal communications, we could use [Remote Procedure Calls](https://githu
|
||||
|
||||
> Identify and address bottlenecks, given the constraints.
|
||||
|
||||

|
||||

|
||||
|
||||
**Important: Do not simply jump right into the final design from the initial design!**
|
||||
|
||||
|
Reference in New Issue
Block a user