System Design: Step-by-step
Keep reading for FREE
There is no single design for any system that works perfectly. There are always trade-offs. Two different people can come up with different designs, with both being excellent given different assumptions.
Your goal is to:
Once you have a basic design in mind, focus on the key issues. Identify the bottlenecks and major challenges of the system, and then adjust your design to handle them.
In the TinyURL example, a challenge you might consider is that some URLs are frequently accessed, while others suddenly peak when they go viral on social media. You don't want to hit the database for every request, so you could add a cache layer.
Depending on the type of system you are designing, you need to estimate its scale: how many users will access it every day, how much data you will store and process, etc.
You should be careful when making assumptions. Incorrect assumptions can dramatically change the design. You should rely on your product sense as well to make reasonable assumptions.
In the TinyURL example:
You can't design a system if you don't know what you're designing.
First, ask questions to clarify what you need to implement. Then make a list of all major features and use cases that your design must cover.
For example, if you're designing TinyURL, that list might be:
Draw a high-level diagram of what your system looks like:
reading habits, gather your
remember what you readand stay ahead of the crowd!
Save time with daily digests
No ads, all content is free
Save ideas & add your own
Get access to the mobile app
4.7 App Rating
Alt account of @ocp. I use it to stash ideas about software engineering
MORE LIKE THIS
Chapter 3 How to influence people and friends