Couchbase Cloud-Native Database
The Couchbase Cloud-Native Database is the native integration of Couchbase Server with cloud-native technologies, facilitated by the Couchbase Autonomous Operator. This integration empowers organizations to build and run scalable stateful applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.
The Couchbase Cloud-Native Database is the culmination of Couchbase Server and native integration with cloud-native open-source technologies such as Kubernetes, Prometheus, Helm, CNI, CoreDNS, Operator Framework, Ceph, Gluster, Istio Service Mesh, and the Open Service Broker API.
Couchbase Autonomous Operator for Kubernetes
The Autonomous Operator is the core product in the Couchbase Cloud-Native Database that has been integrated with various cloud-native technologies as depicted in the diagram above. The Autonomous Operator is a pre-requisite to be able to use the cloud-native integrations.
Prometheus has become the de facto standard for monitoring, especially for Kubernetes deployments. With Couchbase Exporter for Prometheus, users can standardize and centralize their monitoring with Prometheus and Grafana for visualization.
Fluent Bit has become a de facto standard for lightweight log processing and forwarding, allowing for the collection of data like metrics and logs from different sources, enriching them with filters, and sending them to multiple destinations. It’s the preferred choice for containerized environments like Kubernetes. Logs can be forwarded from multiple Couchbase clusters to a centralized logging solution with a standard structure.
An integration with Helm simplifies the user experience through an alternate way of installing the Couchbase Autonomous Operator.
Couchbase provides official Helm charts that deploy various aspects of the Couchbase Cloud-Native Database. The main chart can be used to deploy the whole system or just individual components.
An integration with the Open Service Broker API that provides an alternate way of installing Couchbase Server via the Couchbase Autonomous Operator at the cluster-scope, as well as the namespace-scope. This separation of cluster-scope and namespace-scope provides robust brokered services. Couchbase Service Broker provides a mechanism that allows platform engineers to easily curate a marketplace of services that can be consumed by applications running across many Kubernetes clusters by building on top of the diverse ecosystem of services available today, no matter what platform they’re running on (AKS, EKS, GKE, or On-prem).
Istio is a service mesh that may be used when combining multiple microservices together in the deployments behind applications. A service mesh can, transparent to your services, add security, observability, traffic management, and other capabilities.
Couchbase Autonomous Operator supports Container Network Interface (CNI), which consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins.
Persistent volumes are a fundamental part of stateful applications such as databases that require some form of persistent storage to avoid data loss. Even stateless microservices have some dependency on persistent data stores where the data persists beyond the container, pod, or host. The Couchbase Autonomous Operator supports persistent volumes for Couchbase Server deployments.
TLS support inside of the Kubernetes cluster is driven by CoreDNS, which is a graduated project in the CNCF landscape. The Couchbase Autonomous Operator supports CoreDNS.
The Couchbase Autonomous Operator is compatible with, and runs on, several popular Kubernetes platforms such as Microsoft Azure Kubernetes Service, AWS Elastic Kubernetes Service, Google Kubernetes Engine.