Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

A newer version of this documentation is available.

View Latest

Buckets, Memory, and Storage

      +
      Couchbase Server saves items in Buckets.

      Creating, Maintaining, and Accessing Data

      Couchbase Server keeps items in Buckets. Before an item can be saved, a bucket must exist for it. Buckets can be created by means of the Couchbase Web Console, the REST API, or the CLI. Each bucket is assigned a name at its creation: this name is referenced by the application or user wishing to save or access items within it.

      The types of bucket most frequently used are Couchbase and Ephemeral buckets. Couchbase buckets exist both in memory and on disk. Ephemeral buckets exist only in memory. Buckets can be configured to maintain data in compressed format, so as to maximize resource-effectiveness. Documents within a bucket can be assigned a Time To Live, to ensure that they expire after a specified time-period, and that their data is thus made permanently inaccessible.

      Couchbase Server manages memory to ensure high performance and scalability: memory quotas are established, and data not recently used can be ejected, to make room for data more frequently requested. Multi-threaded readers and writers provide simultaneous read and write operations for data on disk, ensuring high throughput.

      The pages in this section provide detailed descriptions of buckets, memory, and storage.