Install and Start Using the Java SDK with Couchbase Server

The Couchbase Java SDK allows Java applications to access a Couchbase cluster. It offers traditional synchronous APIs as well as reactive and asynchronous APIs to maximize flexibility and performance.

The Couchbase Java SDK 3.0 is a complete rewrite of the API, reducing the number of overloads to present a simplified surface area, and adding support for future Couchbase Server features like Collections and Scopes (available in Couchbase Server 6.5 as a developer preview). The 3.0 SDK also moves from RxJava to Java Reactor, along with other improvements to performance, logging, and timeout troubleshooting. If you’re upgrading your application from Java SDK 2.x, please read our Migrating 2.x code to SDK 3.0 Guide.

Installing the SDK

At least Java 8 is required for current releases; see the Compatibility section for details. We recommend running the latest LTS version (i.e. at the time of writing JDK 11) with the highest patch version available. Java 11 has various enhancements like lambda local variable type inference, profiling tools, and updated security features.

Couchbase publishes all stable artifacts to Maven Central. You can use your favorite dependency management tool to install the SDK. The following snippet shows how to do it with maven.


Hello Couchbase

Once you have the Java client installed, open your IDE, and try out the following:

Cluster cluster = Cluster.connect("localhost", "username", "password");

Couchbase uses Role Based Access Control (RBAC) to control access to resources. Here we will use the Full Admin role created during installation of the Couchbase Data Platform. For production client code, you will want to use more appropriate, restrictive settings — but here we want to get you up and running quickly. If you’re developing client code on the same VM or machine as the Couchbase Server, your URI can be localhost.

If you are not using an IDE or are new to java, the following imports are necessary to build the following snippets:


Connection to the cluster is initialized by

// get a bucket reference
Bucket bucket = cluster.bucket("bucket-name");

If you installed the travel sample data bucket, substitute travel-sample for bucket-name.

// get a collection reference
Collection collection = bucket.defaultCollection();

The 3.0 SDK is ready for the introduction of Collections in an upcoming release of the Couchbase Data Platform. The latest release, Couchbase Server 6.5, brings a limited Developer Preview of Collections, allowing Documents to be grouped by purpose or theme, according to specified Scope. Here we will use the DefaultCollection, which covers the whole Bucket and must be used when connecting to a 6.5 cluster or earlier.

// Upsert Document
MutationResult upsertResult = collection.upsert(
    JsonObject.create().put("name", "mike")

// Get Document
GetResult getResult = collection.get("my-document");

KV Operations are described in detail on the KV Operations page. Now that you know the basics, you may wish to go straight to that page.

You can also perform a N1QL query at the cluster level:

QueryResult result = cluster.query("select \"Hello World\" as greeting");

You can learn more about N1QL queries on the Query page. Other services (like analytics, search or views) work very similar to the two shown above. Please refer to their respective documentation sections to learn more.

Additional Resources

The API reference is generated for each release and can be found here.

Couchbase welcomes community contributions to the Java SDK. The Java SDK source code is available on GitHub.