The Couchbase .NET SDK and related projects. This category is also the appropriate place to discuss framework integration such as ASP.NET or tool integration like ELMAH, Glimpse and others.

The Couchbase Node.js SDK and related projects. Also discussed here are frameworks built with Node for Couchbase, such as Ottoman and Kouch.

Couchbase Java SDK and related projects. This category is also the appropriate place to post topics on Java based integration, such as Spring Data Couchbase, the Couchbase Hadoop Connector, and others.

Discussion of core Couchbase Server, Couchbase Server administration, integration, or core capabilities. If the topic you would like to post is specific to programming with SDKs, Couchbase Mobile or N1QL, please post to that category instead.

This category is for discussion of the Couchbase Go SDK and related projects. Post topics such as questions and discussions on working with Go and Couchbase here.

Couchbase Lite and the Couchbase Sync Gateway. Ask questions, get advice, suggest improvements. However, please submit bug reports to our Github issue trackers instead:

N1QL, the query language from Couchbase. Post questions/topics here related to development, deployment or just general feedback.

This category is for discussion of the Couchbase Python SDK and integration with related frameworks. Post topics such as questions and discussions on working with Python and Couchbase here. Discussion on the use of the Twisted and gevent programming models also occurs here.

Apache Spark is a fast and general-purpose cluster computing system. It provides high-level APIs in Java, Scala, Python and R, and an optimized engine that supports general execution graphs, and supports a rich set of higher-level tools including Spark SQL for SQL and structured data processing,

Elasticsearch provides scalable and speedy search, analytics, and storage. The Couchbase Elasticsearch Connector replicates your documents from Couchbase Server to Elasticsearch in near real time.

This category is for discussion of the Couchbase PHP SDK and related projects. Post topics such as questions and discussions on working with PHP and Couchbase here, including deployment topics with PHP.

Kafka is used for building real-time data pipelines and streaming apps. It is horizontally scalable, fault-tolerant, wicked fast, and runs in production in thousands of companies.

Use this category when discussing anything that is part of CBFT, the Couchbase Full Text server project and components (currently under development). Post questions/topics here related to development, deployment or just general feedback.

This is the community category for discussion on things relevant to the Couchbase community.

Couchbase Eventing enables customers to build better customer engagement by processing interactions in near-real-time.

This category is for discussing Couchbase Analytics. Post questions/topics here related to development, deployment, or general feedback here.

Use this category when discussing the ODBC or JDBC interfaces to SQL for Documents (codename N1QL). Post questions/topics here related to development, deployment or just general feedback.

The Couchbase Scala SDK and related projects.

Use this category when discussing the Couchbase Ruby SDK and related projects. Post topics related to working with Node.js and Couchbase here. Also discussed here is frameworks integration with Ruby for Couchbase, such as Active Model for Couchbase Server.

This category exists for discussing one of the many community driven client libraries. Among many others, Perl, clutchbase and Spyglass for Clojure, cberl for Erlang, and even a TCL client library.

This Category is for discussion on the Couchbase C SDK, also known as libcouchbase. It is used most commonly as a supporting layer for other SDKs, such as the Python, Ruby, Node.js, PHP and several community driven SDKs.

This category is for any other project or products associated with Couchbase that are not appropriate for any other category.

Discussion about this site, its organization, how it works, and how we can improve it. Please offer suggestions and recommendations here on categorization, notification and anything else you'd like to see improved.