Book Image

Learning Couchbase

By : Henry Potsangbam
Book Image

Learning Couchbase

By: Henry Potsangbam

Overview of this book

This book achieves its goal by taking up an end-to-end development structure, right from understanding NOSQL document design to implementing full fledged eCommerce application design using Couchbase as a backend. Starting with the architecture of Couchbase to get you up and running, this book quickly takes you through designing a NoSQL document and implementing highly scalable applications using Java API. You will then be introduced to document design and get to know the various ways to administer Couchbase. Followed by this, learn to store documents using bucket. Moving on, you will then learn to store, retrieve and delete documents using smart client base on Java API. You will then retrieve documents using SQL like syntax call N1QL. Next, you will learn how to write map reduce base views. Finally, you will configure XDCR for disaster recovery and implement an eCommerce application using Couchbase.
Table of Contents (12 chapters)
Index

A Couchbase SDK overview


So far, in the previous chapters, we have understood how to create buckets and store documents in them using the bucket editor via the web admin console. We have also discussed some of the guidelines used for designing document-based database systems.

What if we need to connect and perform operations on the Couchbase cluster from an application? This can be achieved using the Couchbase client libraries, which are also collectively known as Couchbase Software Development Kit (SDK). The Couchbase SDK APIs are language dependent. The concepts remain the same and are applicable to all languages that are supported by the SDK. However, there are some features such as thread safe, asynchronous operations, and so on that are language dependent. For example, thread safe features are tested and certified for Java SDK and .NET SDK, version 1.0 and above.

You can refer to the Couchbase website (http://docs.couchbase.com/developer/dev-guide-3.0/thread-safety.html) for further details...