(3) How should I prepare system design questions for Google/Facebook Interview? - Quora
1) Asynchronous is good (use Queues, Topics etc.)
2) Parallel is good (Multi-threading, load balancing etc.)
3) Avoid points of contention e.g. synchronization
4) Avoid writing to disk until you must - cache like crazy
5) Scale out not up
6) At web scale the speed of light is a problem
7) At web scale everything fails - networks, load balancers etc.
And here are some good articles to read and presentations to watch
http://s3.amazonaws.com/A
High Scalability - High Scalability - Amazon Architecture
http://www.addsimplicity.
Scalability Best Practices: Lessons from eBay
http://www.hpts.ws/papers
http://static.googleuserc
facebook architecture for 600M users
Infrastructure at Facebook
Scaling Memcache at Facebook
Scuba: Diving into Data at Facebook
Unicorn: A System for Searching the Social Graph
http://www.cs.cmu.edu/~pa
Scale at Facebook
Scalability, Availability & Stability Patterns
LinkedIn - A Professional Network built with Java Technologies and ...
LinkedIn Data Infrastructure (QCon London 2012)
Global Netflix Platform
Timelines at Scale
Big Data in Real-Time at Twitter
https://github.com/checkcheckzz/system-design-interview
How should I prepare system design questions for Google/Facebook Interview?
In my view there are two components to solving system design questions at interviews:
1) Having enough knowledge and skills to come up with good solutions
2) Using the right process to approach the questions
The idea is that at an interview you have 30-40 minutes to answer a question like: "How would you design a search engine", or "Create this hierarchy of classes, which does X".
Obviously, to solve such a question in full, companies need weeks to years and big teams of engineers. So, how on Earth should one person answer the question in 30 minutes.
Usually, such a discussion needs to start at the higher level where the interviewee presents their idea of how the architecture would be structured. Only after that, if the interviewer is ok with the higher level design one could go into more details about how they would tackle specific bottlenecks and other limitations. Most often, the interviewer would lead the discussion in one or another direction based on their goals.
In short, it's important to practice doing that for enough system design problems. Just take a few from the internet and give it a try. Here are a few examples:
1) Design a URL shortening service.
2) How would you design the feature in LinkedIn where it computes how many hops there are between you and another person?
3) If you were to design a web platform for online chess games, how would you do that?
As for some good resources to start with, I would recommend this video lecture from prof. David Malan from Harvard, which covers many useful aspects of designing scalable systems:
Read full article from (3) How should I prepare system design questions for Google/Facebook Interview? - Quora
1) Asynchronous is good (use Queues, Topics etc.)
2) Parallel is good (Multi-threading, load balancing etc.)
3) Avoid points of contention e.g. synchronization
4) Avoid writing to disk until you must - cache like crazy
5) Scale out not up
6) At web scale the speed of light is a problem
7) At web scale everything fails - networks, load balancers etc.
And here are some good articles to read and presentations to watch
http://s3.amazonaws.com/A
High Scalability - High Scalability - Amazon Architecture
http://www.addsimplicity.
Scalability Best Practices: Lessons from eBay
http://www.hpts.ws/papers
http://static.googleuserc
facebook architecture for 600M users
Infrastructure at Facebook
Scaling Memcache at Facebook
Scuba: Diving into Data at Facebook
Unicorn: A System for Searching the Social Graph
http://www.cs.cmu.edu/~pa
Scale at Facebook
Scalability, Availability & Stability Patterns
LinkedIn - A Professional Network built with Java Technologies and ...
LinkedIn Data Infrastructure (QCon London 2012)
Global Netflix Platform
Timelines at Scale
Big Data in Real-Time at Twitter
https://github.com/checkcheckzz/system-design-interview
How should I prepare system design questions for Google/Facebook Interview?
In my view there are two components to solving system design questions at interviews:
1) Having enough knowledge and skills to come up with good solutions
2) Using the right process to approach the questions
The idea is that at an interview you have 30-40 minutes to answer a question like: "How would you design a search engine", or "Create this hierarchy of classes, which does X".
Obviously, to solve such a question in full, companies need weeks to years and big teams of engineers. So, how on Earth should one person answer the question in 30 minutes.
Usually, such a discussion needs to start at the higher level where the interviewee presents their idea of how the architecture would be structured. Only after that, if the interviewer is ok with the higher level design one could go into more details about how they would tackle specific bottlenecks and other limitations. Most often, the interviewer would lead the discussion in one or another direction based on their goals.
In short, it's important to practice doing that for enough system design problems. Just take a few from the internet and give it a try. Here are a few examples:
1) Design a URL shortening service.
2) How would you design the feature in LinkedIn where it computes how many hops there are between you and another person?
3) If you were to design a web platform for online chess games, how would you do that?
As for some good resources to start with, I would recommend this video lecture from prof. David Malan from Harvard, which covers many useful aspects of designing scalable systems:
Read full article from (3) How should I prepare system design questions for Google/Facebook Interview? - Quora
