NoSQL - what's that
•Download as PPTX, PDF•
3 likes•2,262 views
The document discusses NoSQL databases as an alternative to SQL databases for big data. It provides an overview of why NoSQL databases were created due to limitations of SQL for large, distributed datasets. It then categorizes and describes some popular NoSQL databases, including key-value stores like Dynamo and Redis, document databases like MongoDB and CouchDB, graph databases like Neo4J and FlockDB, and column-oriented databases like BigTable and HBase. The document also contrasts ACID transactions with the BASE model and eventual consistency used by many NoSQL databases.
More Related Content
What's hot
What's hot (20)
Similar to NoSQL - what's that
Similar to NoSQL - what's that (20)
More from Sergejus Barinovas
More from Sergejus Barinovas (15)
Recently uploaded
Recently uploaded (20)
NoSQL - what's that
- 1. NoSQL – What’s that? SergejusBarinovas | Microsoft MVP @sergejusb, sergejus.blogas.lt
- 2. NoSQL
- 3. WHY?
- 9. NoSQL – open source distributed databases, not relational SQL databases
- 10. NoSQL – not only SQL
- 17. Consistency – state integrity
- 18. Isolation – no reads of uncommitted data
- 19. Durability – recover committed transACID (transactions)
- 21. Availability
- 24. Soft state – inconsistency is OK
- 25. Eventual consistency – stale data is OK BASE (eventual consistency)
- 27. NoSQL Databases
- 30. Graph database
- 33. Simple operationsGet Put Delete Key / value store Key Value Byte[] Byte[]
- 34. Key / value store Key Value “current_date” 2011.01.16 “sergejusb” Binary Object “sergejusb” JSON Object
- 36. Membase
- 37. Voldermort
- 38. Redis
- 40. RiakKey / value store
- 41. Name: Dynamo Created: 2007, Amazon (proprietary) Implementation: ? Distributed: Yes Replication: Multiple Servers CAP: AP API: ? Key / value store
- 42. Name: Membase Created: 2010, sponsored by Zinga Implementation: C / C++ / Erlang Distributed: Yes Replication: Multiple Servers CAP: CP API: Memcached API, JSON Key / value store
- 43. Name: Voldemort Created: 2008, LinkedIn Implementation: Java Distributed: Yes Replication: Multiple Servers CAP: AP API: Java Key / value store
- 44. Name: Redis Created: 2009, sponsored by VMWare Implementation: C Distributed: No Replication: Master / Slave CAP: CP API: Various Languages Key / value store
- 45. Name: Azure Table Storage Created: 2008, Microsoft Implementation: ? Distributed: Yes Replication: Multiple Servers (DFS) CAP: CP API: .NET API, JSON Key / value store
- 46. Name: Riak Created: 2008, Basho (from Akamai) Implementation: Erlang Distributed: Yes Replication: Multiple Servers CAP: AP API: JSON Key / value store
- 48. Schema can be defined at runtime
- 49. Optional support for simple querying using Map / ReduceDocument database
- 51. CouchDB
- 53. Name: MongoDB Created: 2008, 10gen Implementation: C++ Distributed: Yes via Shards Replication: Master / Slave CAP: CP API: BSON Document database
- 54. Name: CouchDB Created: 2005 Implementation: Erlang Distributed: Sort of Replication: Master / Master CAP: AP API: JSON Document database
- 55. Name: RavenDB Created: 2010, AyendeRahien Implementation: C# Distributed: Yes via Shards Replication: Master / Master CAP: AP API: .NET API, JSON Document database
- 57. Basic constructsNode Edge Properties Graph database sergejus.blogas.lt reads authors knows sergejus tdagys knows
- 60. Name: FlockDB Created: 2010, Twitter Implementation: Scala Distributed: Yes Replication: Multiple Servers CAP: AP API: Thrift, Ruby Graph database
- 61. Name: Neo4J Created: 2003, NeoTechnologies Implementation: Java Distributed: No Replication: Master / Slave CAP: CP API: JSON, Various Languages Graph database
- 63. Columns are added at a runtime
- 64. Great scalability Horizontal Vertical Columnar database
- 67. Cassandra
- 68. HBase
- 70. Name: BigTable Created: 2006, Google Implementation: C++ Distributed: Yes Replication: Multiple Servers (GFS) CAP: CP API: C++ Columnar database
- 71. Name: Cassandra Created: 2008, Facebook Implementation: Java Distributed: Yes Replication: Multiple Servers CAP: AP API: Thrift, Avro Columnar database
- 72. Name: HBase Created: 2007, Powerset Implementation: Java Distributed: Yes Replication: Multiple Servers (HDFS) CAP: CP API: Thrift, Java, JSON Columnar database
- 73. Name: Hypertable Created: 2007, Zvents Implementation: C Distributed: Yes Replication: Multiple Servers CAP: CP API: Thrift Columnar database
- 79. Tooling
- 82. You can use BOTHSQL vs. NoSQL
- 83. Q & A
Editor's Notes
- Atomicity. All of the operations in the transaction will complete, or none will.Consistency. The database will be in a consistent state when the transaction begins and ends.Isolation. The transaction will behave as if it is the only operation being performed upon the database.Durability. Upon completion of the transaction, the operation will not be reversed.
- Consistency. The client perceives that a set of operations has occurred all at once.Availability. Every operation must terminate in an intended response.Partition tolerance. Operations will complete, even if individual components are unavailable.http://www.cs.berkeley.edu/~brewer/cs262b-2004/PODC-keynote.pdf
- Basically Available. Supportingpartial failures without total system failure.Soft state. The state can be inconsistent for a given period of time.Eventual consistency. After some time all replicas will have consistent data.For a given accepted update and a given replica eventually either the update reaches the replica or the replica retires from service
- http://labs.google.com/papers/bigtable.htmlhttp://labs.google.com/papers/gfs.htmlhttp://s3.amazonaws.com/AllThingsDistributed/sosp/amazon-dynamo-sosp2007.pdf