UT Dallas CS 6350 - 07.NOSQL-CAP (23 pages)

Previewing pages 1, 2, 22, 23 of 23 page document View the full content.
View Full Document

07.NOSQL-CAP



Previewing pages 1, 2, 22, 23 of actual document.

View the full content.
View Full Document
View Full Document

07.NOSQL-CAP

111 views


Pages:
23
School:
University of Texas at Dallas
Course:
Cs 6350 - Big Data Management and Analytics
Big Data Management and Analytics Documents

Unformatted text preview:

NoSQL Databases Slides take from J Pokorn KSI MFF UK 1 Cloud computing cloud databases Cloud computing data intensive applications on hundreds of thousands of commodity servers and storage devices basic features elasticity fault tolerance automatic provisioning Cloud databases traditional scaling up adding new expensive big servers is not possible requires higher level of skills is not reliable in some cases Architectural principle scaling out or horizontal scaling based on data partitioning i e dividing the database across many inexpensive machines DATAKON 2011 J Pokorn 2 Cloud computing cloud databases Technique data sharding i e horizontal partitioning of data e g hash or range partitioning Consequences manage parallel access in the application scales well for both reads and writes not transparent application needs to be partition aware DATAKON 2011 J Pokorn 3 Relaxing ACID properties Cloud computing ACID is hard to achieve moreover it is not always required e g for blogs status updates product listings etc Availability Traditionally thought of as the server process available 99 999 of time For a large scale node system there is a high probability that a node is either down or that there is a network partitioning Partition tolerance ensures that write and read operations are redirected to available replicas when segments of the network become disconnected DATAKON 2011 J Pokorn 4 Eventual Consistency Eventual Consistency When no updates occur for a long period of time eventually all updates will propagate through the system and all the nodes will be consistent For a given accepted update and a given node eventually either the update reaches the node or the node is removed from service BASE Basically Available Soft state Eventual consistency properties as opposed to ACID Soft state copies of a data item may be inconsistent Eventually Consistent copies becomes consistent at some later time if there are no more updates to that data item Basically Available



View Full Document

Access the best Study Guides, Lecture Notes and Practice Exams

Loading Unlocking...
Login

Join to view 07.NOSQL-CAP and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view 07.NOSQL-CAP and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?