Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Couchbase Essentials

By : John C Zablocki

3 (2)

Couchbase Essentials

3 (2)

By: John C Zablocki

Overview of this book

This book is for those application developers who want to achieve greater flexibility and scalability from their software. Whether you are familiar with other NoSQL databases or have only used relational systems, this book will provide you with enough background to move you along at your own pace. If you are new to NoSQL document databases, the design discussions and introductory material will give you the information you need to get started with Couchbase.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Getting Comfortable with Couchbase

1. Getting Comfortable with Couchbase

The NoSQL landscape

NoSQL taxonomies

Installing Couchbase

Ports

Running Couchbase for the first time

Exploring the Couchbase Console

Couchbase architecture

Couchbase SDKs

RAM matters

Summary

2. Using Couchbase CRUD Operations

2. Using Couchbase CRUD Operations

The Couchbase SDKs

Basic operations

Advanced CRUD operations

Storing complex types

Concurrency and locking

Asynchronous operations

Durability operations

Summary

3. Creating Secondary Indexes with Views

3. Creating Secondary Indexes with Views

Couchbase documents

Couchbase indexes

MapReduce

Couchbase views

Couchbase Console

Querying views

Couchbase SDKs and views

Summary

4. Advanced Views

4. Advanced Views

Querying by type

Nested collections

Range queries

Multiple keys per document

Compound indexes

Grouping keys

Emitting values

Querying with beer-sample

Summary

5. Introducing N1QL

5. Introducing N1QL

Installing N1QL

Simple queries

Null or missing properties

String utilities

Aggregation and math

Complex structures

Working with collections

Joins

SDK support

Summary

6. Designing a Schema-less Data Model

6. Designing a Schema-less Data Model

Key design

Document design

Summary

7. Creating a To-do App with Couchbase

7. Creating a To-do App with Couchbase

A simple to-do schema

Working with SDKs

Creating a task

Listing tasks

Showing only incomplete tasks

Nested tasks

Summary

A. Couchbase SDKs

A. Couchbase SDKs

Couchbase Java SDK

Couchbase .NET SDK

Couchbase PHP SDK

The Couchbase Node.js SDK

Couchbase Python SDK

Couchbase Ruby SDK

Couchbase C SDK

Index

Index

Customer Reviews

3 (2)

5 star

0

4 star

50%

3 star

0

2 star

50%

1 star

0

Key design

With Couchbase, you can't have a document without a key. Therefore, it's clearly important to have a strategy for key design. How you choose to generate your keys will, generally, be partly preference driven and partly use case driven. We'll start by examining what basic requirements exist for keys in Couchbase.

Keys, metadata, and RAM

We saw previously that Couchbase keys are parts of the metadata of a document. This fact was revealed as we explored views that used the meta argument in map functions to retrieve document IDs for indexes. Prior to Couchbase Server 3.0, all keys were kept in the memory even if their documents weren't. Therefore, longer keys required more memory. Since Couchbase performs best when documents are kept in the memory, smaller keys mean more RAM available for documents.

In Couchbase Server 3.0, keeping metadata in the memory is still the default behavior, but it is now tunable. While you're now able to delete metadata from the...

Search

Your notes and bookmarks