1. NoSQL Cheng Lei rexlei86@uvic.ca Department of Electrical and Computer Engineering University of Victoria Mar 05, 2015

2. Outline ❖ Why NoSQL? ❖ Aggregate Data Model ❖ Distribution Model

3. ❖ Why NoSQL? ❖ Aggregate Data Model ❖ Distribution Model

4. Why NoSQL ? Impedance mismatch the difference between the relational model and the in-memory data structures Working on clusters: More sufficiently Schemaless Opensource

5. ❖ Why NoSQL? ❖ Aggregate Data Model ❖ Distribution Model

6. Aggregate Data Model Aggregate: an aggregate is a collection of related objects treated as a unit.

7. Key-Value Data Model The aggregate is opaque to DB, just some big blob of mostly meaningless bits Access aggregates by lookup based on the keys

8. Document Data Model The aggregate is built by the structure of the document

9. Column-Family Stores It is a two-level map The first key is often described as a row identifier Second-level values are referred to as columns

10. ❖ Why NoSQL? ❖ Aggregate Data Model ❖ Distribution Model

11. Distribution Models Single server Sharding Master-Slave Replication Peer-to-Peer Replication Combining Sharding & Replication

12. Sharding Putting different parts of data onto different servers

13. Master-Slave Replication One node as the master, controlling the operations on the rest nodes All changes are made to the master The master propagates the changes to slaves The slave node can be assigned as the master if master fails

14. Peer-to-Peer Replication Reads and writes on each single server Each node synchronizes the writes with each other Consistency issues may occur

15. Combining Sharding & Replication Master-Slave replication &sharding Multiple masters Each data item only has single master Peer-to-Peer replication & Sharding Make 3 copies of node data

16. Thank You!!!