2. Why NoSQL?
• A NoSQL or “non relational” database reduces the need for
developers to maintain separate caching layers or write and
maintain sharding code.
• Supports Dynamic schemas with their polyglot persistence
architecture.
• Supports auto-sharding, replication and integrated caching.
3. Types of NoSQL?
• Key-value stores such as Redis, Riak.
• Document databases such as Couchbase, MongoDB.
• Wide-column stores such as Cassandra and Hbase.
• Graph stores such as Neo4J and HyperGraphDB.
5. Where does Couchbase lie down in CAP?
• The 'CAP' behaviour of Couchbase Server as a single cluster vs Couchbase
Server with XDCR is different.
• Couchbase Server is mainly referred to as a CP system.
• With a multi-cluster deployment with XDCR, Couchbase Server provides
you AP.
6. What is Couchbase?
• Open Source Key-Value NoSQL database that can act as a fully
functional NoSQL JSON document store.
• As it is a NoSQL technology you do not have a schema.
• It uses “buckets” as the containers for data storage.
• Couchbase Server uses buckets to group collections of keys and
values logically.
8. What is a Bucket?
• Equivalent of a database.
• Protected by the Couchbase Role-Based Access Control (RBAC) system.
• Cluster can have multiple buckets, each with its own memory quota,
number of replica copies, and capabilities.
• Data stored automatically replicate for high availability, using
the Database Change Protocol (DCP) and dynamically scaled across
multiple servers, by means of Cross Datacentre Replication (XDCR).
9. What is a Document?
• Documents are simply
Couchbase’ s term for the
information that’s associated
with a key.
• Think of a document as “Row” of
data.
• Each document stored in a data
bucket must have a unique
document ID, which is similar to
the concept of a SQL primary key.
10. Moving from Oracle to Couchbase
• Couchbase offers a SQL-like
language “N1QL” that would
seem very familiar to an RDBMS
user.
• Data Modelling.
• Couchbase Java SDK.
• Query Workbench.
12. Cross Datacentre Replication (XDCR)
• Cross Datacentre Replication
(XDCR) provides an easy way to
replicate data from one cluster to
another.
• XDCR provides automatic conflict
resolution.
• XDCR only replicates data, it does
not replicate views or indexes.