SDK Extension Libraries
Field Level Encryption, Response Time Observability (Tracing), and Transactions libraries ship separately from each SDK. As does Spring Data and others which are not applicable for each SDK. These pages are for common material across a number of SDKs.
If you have landed on this page, you most likely wish to be on a general page for one of the extension libraries. These are outlined in the next section. If you want to be on a particular SDK’s extension library page, you will find them listed at the end of the page.
Couchbase provides several SDKs to allow applications to access a Couchbase cluster, as well as Mobile SDKs to carry your application to the edge.
Distributed ACID Transactions are operations that ensure that when multiple documents need to be modified such that only the successful modification of all justifies the modification of any, either all the modifications do occur successfully; or none of them occurs.
Fields within a JSON document can be securely encrypted by the SDK to support FIPS 140-2 compliance. This is a client-side implementation, with encryption and decryption handled by the Couchbase client SDK.
Health indicators can tell you a lot about the performance of an application. Monitoring them is vital both during its development and production lifecycle. For a database, performance is best encapsulated via per-request performance.
Spring Data for Couchbase is part of the umbrella Spring Data project which aims to provide a familiar and consistent Spring-based programming model for new datastores while retaining store-specific features and capabilities.
The Spring Data Couchbase project provides integration with the Couchbase Server database and any of our JVM SDKs. Key functional areas of Spring Data Couchbase are a POJO centric model for interacting with Couchbase Buckets or Collections, and easily writing a Repository style data access layer.