Add pandoc for PDF creation and GitHub Actions for auto-generation

This commit is contained in:
Rick Calixte
2021-12-26 02:00:40 -05:00
parent 3df19b2e4f
commit f733e5970e
32 changed files with 1092 additions and 169 deletions

View File

@@ -80,7 +80,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/E8klrBh.png)
![High level design of Mint.com](https://i.imgur.com/E8klrBh.png)
## Step 3: Design core components
@@ -327,7 +327,7 @@ class SpendingByCategory(MRJob):
> Identify and address bottlenecks, given the constraints.
![Imgur](http://i.imgur.com/V5q57vU.png)
![Scaled design of Mint.com](https://i.imgur.com/V5q57vU.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -79,7 +79,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/BKsBnmG.png)
![High level design of Pastebin.com (or Bit.ly)](https://i.imgur.com/BKsBnmG.png)
## 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.
![Imgur](http://i.imgur.com/4edXG0T.png)
![Scaled design of Pastebin.com (or Bit.ly)](https://i.imgur.com/4edXG0T.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -58,7 +58,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/KqZ3dSx.png)
![High level of a key-value cache to save the results of the most recent web server queries](https://i.imgur.com/KqZ3dSx.png)
## 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.
![Imgur](http://i.imgur.com/4j99mhe.png)
![Scaled design of a key-value store for a search engine](https://i.imgur.com/4j99mhe.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -70,7 +70,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/vwMa1Qu.png)
![High level design of Amazon's sales ranking by category feature](https://i.imgur.com/vwMa1Qu.png)
## 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.
![Imgur](http://i.imgur.com/MzExP06.png)
![Scaled design of Amazon's sales ranking by category feature](https://i.imgur.com/MzExP06.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -64,7 +64,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/B8LDKD7.png)
![High level design of an AWS service](https://i.imgur.com/B8LDKD7.png)
## 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+
![Imgur](http://i.imgur.com/rrfjMXB.png)
![Scaled design of an AWS service to lighten load on a single box and allow for independent scaling](https://i.imgur.com/rrfjMXB.png)
#### Assumptions
@@ -191,7 +191,7 @@ We've been able to address these issues with **Vertical Scaling** so far. Unfor
### Users++
![Imgur](http://i.imgur.com/raoFTXM.png)
![Scaled design of an AWS service to address web server scaling](https://i.imgur.com/raoFTXM.png)
#### Assumptions
@@ -220,7 +220,7 @@ Our **Benchmarks/Load Tests** and **Profiling** show that our single **Web Serve
### Users+++
![Imgur](http://i.imgur.com/OZCxJr0.png)
![Scaled design of an AWS service to address MySQL scaling](https://i.imgur.com/OZCxJr0.png)
**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++++
![Imgur](http://i.imgur.com/3X8nmdL.png)
![Scaled design of an AWS service with autoscaling added](https://i.imgur.com/3X8nmdL.png)
#### Assumptions
@@ -297,7 +297,7 @@ Our **Benchmarks/Load Tests** and **Profiling** show that our traffic spikes dur
### Users+++++
![Imgur](http://i.imgur.com/jj3A5N8.png)
![Scaled design of a system that scales to millions of users on AWS](https://i.imgur.com/jj3A5N8.png)
**Note:** **Autoscaling** groups not shown to reduce clutter

View File

@@ -50,7 +50,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/wxXyq2J.png)
![High level design of the data structures for a social network](https://i.imgur.com/wxXyq2J.png)
## 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.
![Imgur](http://i.imgur.com/cdCv5g7.png)
![Scaled design of the data structures for a social network](https://i.imgur.com/cdCv5g7.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -93,7 +93,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/48tEA2j.png)
![High level design of the Twitter timeline and search (or Facebook feed and search)](https://i.imgur.com/48tEA2j.png)
## 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.
![Imgur](http://i.imgur.com/jrUBAF7.png)
![Scaled design of the Twitter timeline and search (or Facebook feed and search)](https://i.imgur.com/jrUBAF7.png)
**Important: Do not simply jump right into the final design from the initial design!**

View File

@@ -69,7 +69,7 @@ Handy conversion guide:
> Outline a high level design with all important components.
![Imgur](http://i.imgur.com/xjdAAUv.png)
![High level design of a web crawler](https://i.imgur.com/xjdAAUv.png)
## 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.
![Imgur](http://i.imgur.com/bWxPtQA.png)
![Scaled design of a web crawler](https://i.imgur.com/bWxPtQA.png)
**Important: Do not simply jump right into the final design from the initial design!**