gaspersic/coding-interview-university
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added better system design outline. Added it to cheat sheets.

Browse Source
This commit is contained in:
John Washam 2016-09-14 11:01:41 -07:00
parent feee65a152
commit 4a06d2e404
2 changed files with 29 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@ -948,12 +948,27 @@ You'll get more graph practice in Skiena's book (see Books section below) and th
- Timelines at Scale: https://www.infoq.com/presentations/Twitter-Timeline-Scalability - Timelines at Scale: https://www.infoq.com/presentations/Twitter-Timeline-Scalability
- [x] Practicing the system design process: Here are some ideas to try working through on paper, each with some documentation on how it was handled in the real world: - [x] Practicing the system design process: Here are some ideas to try working through on paper, each with some documentation on how it was handled in the real world:
- review: System Design from HiredInTech: http://www.hiredintech.com/system-design/ - review: System Design from HiredInTech: http://www.hiredintech.com/system-design/
- [cheat sheet](https://github.com/jwasham/google-interview-university/blob/master/extras/cheat%20sheets/system-design.pdf)
- flow: - flow:
- ask about constraints 1. Understand the problem and scope:
- determine use cases - define the use cases, with interviewer's help
- abstract, high level design - suggest additional features
- bottlenecks - remove items that interviewer deems out of scope
- scaling - assume high availability is required, add as a use case
2. Think about constraints:
- ask how many requests per month
- ask how many requests per second (they may volunteer it or make you do the math)
- estimate reads vs. writes percentage
- keep 80/20 rule in mind when estimating
- how much data written per second
- total storage required over 5 years
- how much data read per second
3. Abstract design:
- layers (service, data, caching)
- infrastructure: load balancing, messaging
- rough overview of any key algorithm that drives the service
- consider bottlenecks and determine solutions
- Exercises:
- Design a CDN network: http://repository.cmu.edu/cgi/viewcontent.cgi?article=2112&context=compsci - Design a CDN network: http://repository.cmu.edu/cgi/viewcontent.cgi?article=2112&context=compsci
- Design a random ID generation system: https://blog.twitter.com/2010/announcing-snowflake - Design a random ID generation system: https://blog.twitter.com/2010/announcing-snowflake
- Design a key-value database: http://www.slideshare.net/dvirsky/introduction-to-redis - Design a key-value database: http://www.slideshare.net/dvirsky/introduction-to-redis

BIN
extras/cheat sheets/system-design.pdf Normal file
View File

Binary file not shown.