Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Current weather information
2 Weather Forecast
3ocation Search
4 Personalization
5 API Integration
List non-functional requirements for the system...
1 System should be highly scalable
2 System should be fault tolorrent
3 system hound have low latency
Estimate the scale of the system you are going to design...
Let’s assume there are 10^8 DAU the qps 10^8 /10^5 =10^3
Define what APIs are expected from the system...
Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...
As the system is write heavy as every second the weather can change so we will use nosql daytabase like mongodb which will have the following structure
{
“_id”:,
”temprature”:
”wind”,
”humidity”,
”precipitation “
"timestamp"
}
this will be sample structure of the document
You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...
A users logs in to application we will use Aws cognito service for authentication after successfull authentication the call will go to load balancer which will the forward the request to any one of the api server the api server will then forward the call to mongodb which will query the details and respond it back to user. We will add a messaging queue such as rabbitmq or we can also introduce kafka between api server and mongodb so the communication is asynchronous
Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your
A users logs in to application we will use Aws cognito service for authentication after successfull authentication the call will go to load balancer which will the forward the request to any one of the api server the api server will then forward the call to mongodb which will query the details and respond it back to user We will add a messaging queue such as rabbitmq or we can also introduce kafka between api server and mongodb so the communication is asynchronous
Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...
As Mongodb is easily scalable and we will shart the database on the basis of composite shard key that is tempreate and timestamp using this we can ealisy scale the database and using messaging queue or kafka the system is asynchronous so the databse and api server can scale independently
Explain any trade offs you have made and why you made certain tech choices...
As we have used database as mongoddb there can be chances of reading stale data from mongodb
Using sql or relationdatabse the chances of stale read wil be very less but the write performance will suffer as mysql is not suitable for write heavy system
Try to discuss as many failure scenarios/bottlenecks as possible.
For Failure scenarios we will monitor all the failure scenario using promothesis and grafana
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?
We can easily introduce new metrics because of mondodb docuement style model