![]() ![]() Read Write ratio - Determines whether the system is read-heavy or not.Īfter discussing the data and the actions that a user can perform to interact with the system.A service that is read-heavy can be scaled to handle high traffic of requests. The number of requests to the service - To know how to scale the services.Based on the data modality: A rough estimate of how much data must be stored - To know what type of database can be used and file storage for storing images/videos.Latency: Response time of a user action such as loading a web page, liking a post, etc.Any banking system favors consistency over availability as there cannot be discrepancies in data (account balance). Consistency: The systems with high availability will have eventual consistency.High availability: Most of the systems must be highly available.What functionalities can the system or application provide to the user? Example: In Twitter, a user can follow another user, tweet, like a tweet, retweet other’s tweet, and share a tweet (focus on the essential features and do not delve into the complex features of Twitter)įor any distributed system, the following are the fundamental concepts to consider: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |