High-level design

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...

The high level design will have the client which will have a load balancer in between in order to do operations based on many horizontally scaled apis. Th load balancer will get a request from the client and in a round robin fashion so that no server is too overloaded send the request to an API. The apis will be serverless so that we can horizontally scale them easily. The server will retrive data from a database in order which will contain all of the relevant information. Which the server will then send back to the client. The DB will be a NOSql DB so that we can have Consistency and Partitioning like a MongoDB. We can horizontally scale MongoDB efficiently and even though SQL is more structured for this case we will need to use MongoDB to handle the amount of queries to the DB. Also it will make sure that when the db may go down for a second another one can take its place. And users need consistent data. Also we will make sure that the field is Unique by making the field in the db unique. For read heavy we will also add a caching layer in front of the DB so the tiny urls that are constantly used can access the cache rather then straining the DB.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10