Evaluation of Megastore
Recap how the proposed design fulfills the non-functional requirements.
We'll cover the following...
To meet our functional requirements, we employed a variety of strategies. However, we must determine if we have met the non-functional requirements. We’ll go through some techniques we’ve used to meet non-functional requirements.
Megastore was one of the first storage systems to use replication via Paxos to ensure data consistency between data centers. It also meets the demands for scalability and performance for cloud-based web applications. Partitioning the database into entity group sub-databases provides conventional transactional characteristics for the majority of operations while permitting storage and throughput scalability.
Megastore divides the data into numerous mini databases. A replicated log in a NoSQL datastore is implemented for each of them. To increase the overall speed of the underlying datastore and to upscale our replication strategy, Megastore provides applications with fine-grained control over data-partitioning and locality. In an ...