mirrors
/
system-design-primer
mirror of https://github.com/donnemartin/system-design-primer.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Improve punctuation and formatting in README 

Enhanced punctuation and formatting in the README.
These changes enhance the document’s clarity and maintain a uniform structure.
pull/1051/head
Shay Molcho 2025-01-23 12:05:51 +02:00 committed by GitHub
parent 40d5d2edcc
commit 95320c41c9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -50,7 +50,7 @@ Additional topics for interview prep:
<br/> <br/>
</p> </p>
The provided [Anki flashcard decks](https://apps.ankiweb.net/) use spaced repetition to help you retain key system design concepts. The provided [Anki flashcard decks](https://apps.ankiweb.net/) use spaced repetition to help you retain key system design concepts:
* [System design deck](https://github.com/donnemartin/system-design-primer/tree/master/resources/flash_cards/System%20Design.apkg) * [System design deck](https://github.com/donnemartin/system-design-primer/tree/master/resources/flash_cards/System%20Design.apkg)
* [System design exercises deck](https://github.com/donnemartin/system-design-primer/tree/master/resources/flash_cards/System%20Design%20Exercises.apkg) * [System design exercises deck](https://github.com/donnemartin/system-design-primer/tree/master/resources/flash_cards/System%20Design%20Exercises.apkg)
@ -225,7 +225,7 @@ You can use the following steps to guide the discussion. To help solidify this
### Step 1: Outline use cases, constraints, and assumptions ### Step 1: Outline use cases, constraints, and assumptions
Gather requirements and scope the problem. Ask questions to clarify use cases and constraints. Discuss assumptions. Gather requirements and scope the problem. Ask questions to clarify use cases and constraints. Discuss assumptions:
* Who is going to use it? * Who is going to use it?
* How are they going to use it? * How are they going to use it?
@ -238,7 +238,7 @@ Gather requirements and scope the problem. Ask questions to clarify use cases a
### Step 2: Create a high level design ### Step 2: Create a high level design
Outline a high level design with all important components. Outline a high level design with all important components:
* Sketch the main components and connections * Sketch the main components and connections
* Justify your ideas * Justify your ideas
@ -1116,7 +1116,7 @@ Reasons for **NoSQL**:
* Very data intensive workload * Very data intensive workload
* Very high throughput for IOPS * Very high throughput for IOPS
Sample data well-suited for NoSQL: Sample data well-suited for **NoSQL**:
* Rapid ingest of clickstream and log data * Rapid ingest of clickstream and log data
* Leaderboard or scoring data * Leaderboard or scoring data