When a user taps on the search bar we have to show the last 10 unique recent searches made by him/her. The time for the service to respond should be as low as possible given that user upon tapping the search bar would not want to wait for recent searches to load.
Design the ingestion pipeline, the core API service, caching , delegation if required and decide on the high level dataflow.
The problem statement is something to start with, be creative and dive into the product details and add constraints and features you think would be important.
- fetch last 10 unique recent searches made by the user
- response time of the API should be < 10ms
- make your high-level components operate with high availability
- ensure that the data in your system is durable, not matter what happens
- define how your system would behave while scaling-up and scaling-down
- make your system cost-effective and provide a justification for the same
- describe how capacity planning helped you made a good design decision
- think about how other services will interact with your service
- ensure the data in your system is never going in an inconsistent state
- ensure your system is free of deadlocks (if applicable)
- ensure that the throughput of your system is not affected by locking, if it does, state how it would affect
Create a design document of this system/feature stating all critical design decisions, tradeoffs, components, services, and communications. Also specify how your system handles at scale, and what will eventually become a chokepoint.
Do not create unnecessary components, just to make design look complicated. A good design is always simple and elegant. A good way to think about it is if you were to create a spearate process/machine/infra for each component and you will have to code it yourself, would you still do it?
To understand the nuances and internals of this system, build a prototype that
- prototype the entre recent searches flow on local machine
This is a recommended tech-stack for building this prototype
| Which | Options |
|---|---|
| Language | Golang, Java, C++ |
| Database | decide |
| Caching | decide |
These are the common pitfalls that you should keep in mind while you are building this prototype
- delegate whenever possible
- importance of delegation
- designing data flow
- designing a service with SLA < 10ms
If you find this assignment helpful, please
- share this assignment with your friends and peers
- star this repository and help it reach a wider audience
- give me a shoutout on Twitter @arpit_bhayani, or on LinkedIn at @arpitbhayani.
This assignment is part of Arpit's System Design Masterclass - A masterclass that helps you become great at designing scalable, fault-tolerant, and highly available systems.