> For the complete documentation index, see [llms.txt](https://cfcouchbase.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cfcouchbase.ortusbooks.com/overview.md). # Overview The CFCouchbase SDK is a CFML library for interacting with [Couchbase NoSQL Server](http://www.couchbase.com). It can be used by any CFML application or CFML framework to provide them with NoSQL, distributed caching, dynamic queries and many more capabilities. The CFCouchbase SDK wraps the Couchbase Java SDK and enhances it to provide with a nice dynamic language syntax and usability. ## Couchbase SDK Version The Couchbase SDK Version used is 2.2.6 ## Capabilities * Lightweight, standalone library can be used with any CFML application or CFML framework * High performance * Asynchronous calls * Auto-sharding of documents evenly across cluster * 24/7 uptime via on-the-fly node removal and rebalance operations * Easily configurable * Fully-featured API includes view management and execution * Built on the official Java SDK, but customized to take advantage of CFML * Optimistic concurrency control (Documents are not locked by default for maximum throughput) * Conflict management via Compare And Swap (CAS) mechanism * Full cluster and document stats available * Provides direct access to underlying Java SDK for advanced usage * Ability to create as many Couchbase clients as necessary --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cfcouchbase.ortusbooks.com/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.