CouchDB Lightning Talk at BTVWAG's NoSQLvember

CouchDB is a non-relational alternative to data persistence 
for modern software applications.

Transcript

1. CouchDB A Non-Relational Alternative to Data Persistence for Modern Software Applications
2. Is CouchDB a good choice for your application?
3. Problem: The Object-Relational Impedance Mismatch[1] How to persist data in an object-oriented software application? 1. http://c2.com/cgi/wiki?ObjectRelationalImpedanceMismatch 2. http://martinfowler.com/eaaCatalog/repository.html 3. http://c2.com/cgi/wiki?ObjectRelationalMapping
4. separate domain and data mapping layers[2] Problem: The Object-Relational Impedance Mismatch[1] How to persist data in an object-oriented software application? object-relational mapping (ORM)[3] non-relational database 1. http://c2.com/cgi/wiki?ObjectRelationalImpedanceMismatch 2. http://martinfowler.com/eaaCatalog/repository.html 3. http://c2.com/cgi/wiki?ObjectRelationalMapping
5. separate domain and data mapping layers[2] Problem: The Object-Relational Impedance Mismatch[1] How to persist data in an object-oriented software application? object-relational mapping (ORM)[3] non-relational database 1. http://c2.com/cgi/wiki?ObjectRelationalImpedanceMismatch 2. http://martinfowler.com/eaaCatalog/repository.html 3. http://c2.com/cgi/wiki?ObjectRelationalMapping
6. Problem: Semi-Structured Data How to persist data with exible schemas?
7. leave non-applicable column values null Problem: Semi-Structured Data How to persist data with exible schemas? use the entity-attribute- value (EAV) anti-pattern[1] use a schema-less database with a self-describing structure 1. http://pragprog.com/book/bksqla/sql-antipatterns
8. leave non-applicable column values null Problem: Semi-Structured Data How to persist data with exible schemas? use the entity-attribute- value (EAV) anti-pattern[1] use a schema-less database with a self-describing structure 1. http://pragprog.com/book/bksqla/sql-antipatterns
9. Problem: Achieving High Concurrency How to give up consistency in exchange for high availability? [1] 1. http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
10. reduce transaction scope Problem: Achieving High Concurrency How to give up consistency in exchange for high availability? [1] database replication multi-version concurrency control (MVCC) 1. http://www.julianbrowne.com/article/viewer/brewers-cap-theorem denormalization
11. reduce transaction scope Problem: Achieving High Concurrency How to give up consistency in exchange for high availability? [1] database replication multi-version concurrency control (MVCC) 1. http://www.julianbrowne.com/article/viewer/brewers-cap-theorem denormalization
12. About CouchDB
13. • stores self-contained JSON documents • related entities can be stored in a single document • only store elds that are needed in each document Schema-Less
14. • queries are run against indexed views • views are generated through incremental Map functions • aggregate results can be retrieved through Reduce functions CouchDB Views
15. HTTP API • every language and platform has an HTTP client • uses existing semantics (e.g. 201 Created, 202 Accepted) • distributed, scalable and cacheable
16. Map/Reduce
17. Map Book Titles
18. Map Book Authors
19. Map/Reduce gives you tremendous exibility, but has its limitations: no ad-hoc queries* index is one dimensional only key or range queries are allowed† *Temporary views are only useful in development, not in production. †Multiple key queries are allowed, but result in multiple hits on the index.
20. Scaling & Replication
21. Horizontally Scalable • shared nothing architecture • non-blocking reads and writes for high concurrency • fault tolerant, isolated messages
22. Multi-Master Replication • peer-based and bi-directional • no explicit cluster setup required • synchronization is incremental • changes feed allows for replication to other systems
23. Device Synchronization
24. http://oreilly.com/catalog/9781449303129/ http://oreilly.com/catalog/9781449303433/
25. Thank You @BradleyHolt http://bradley-holt.com bradley.holt@foundline.com Copyright © 2011-2013 Bradley Holt. All rights reserved.