Database management

Couchbase automates the management of cloud native databases

NoSQL Database vendor Couchbase advanced its cloud native database deployment efforts with the release of the Autonomous Operator for Kubernetes 2.0 update.

Kubernetes, an open source container orchestration system, is a fundamental part of cloud native environments. With cloud native, businesses can run the same software across multiple cloud providers, as well as on-premises deployments, giving administrators more opportunities to automate database management.

An operator defines and activates a mechanism to package, deploy and manage an application in a stand-alone approach. Many database vendors, including DataStax, NuoDB, and CockroachDB, among others, have also adopted the Kubernetes operator model.

According to IDC analyst Carl Olofson, Couchbase is one of the leading database management systems that run in containers managed by Kubernetes, leveraging the ability to scale resources dynamically. He noted that Couchbase’s new operator is notable for offering enhanced security features, extended support for geographically distributed databases through Cross-Data Center Replication (XDCR), and streamlined operations such as than automated backup.

Overall, Olofson said he sees Kubernetes operators as part of a larger trend in the cloud-native database market.

However, “it will take longer for databases that support data structures with complex internal data dependencies, such as fully relational data warehouses, to be able to take full advantage of the model’s autoscaling capabilities. container, ”said Olofson.

Couchbase Autonomous Operator 2.0 divides up different administrative roles to give organizations more control over management.

How Couchbase Evolved Its Cloud Native Database Approach

Couchbase was one of the first to adopt the Operator approach, releasing its first Kubernetes Operator in August 2018.

The new 2.0 update expands what the Couchbase operator allows in a number of critical areas, including overall management. Kumar said that prior to Update 2.0, the operator only defined one role, that of Cluster Administrator.

“The cluster administrator would basically configure the entire cluster with each configuration,” said Anil Kumar, director of product management at Couchbase.

Couchbase customers told the company there was also a need for more fine-grained controls, as they didn’t want a single cluster administrator to manage multiple resources. Kumar explained that Operator 2.0 now offers the ability to define more specific control for the administration of clusters, users, backups and replication.

Databases that support data structures with complex internal data dependencies, such as fully relational data warehouses, will take longer to take full advantage of the autoscaling capabilities of container mode.

Carl OlofsonAnalyst, IDC

Cloud native security is enhanced

When Couchbase first defined operator requirements, the supplier identified sourcing, on-demand scaling, self-repair and recovery as the main elements, Kumar noted. Security was not on the initial list, but was set to be included in version 2.0.

With the first version of the stand-alone operator Couchbase, the operator created the Couchbase cluster, but the administrator then had to take additional steps to create users and assign roles and permissions.

In 2.0, this process is fully automated with a configuration file that can enable role-based access control (RBAC) for cluster deployments. The new operator can also integrate with existing user directory technology such as Lightweight Directory Access Protocol (LDAP) to further automate the process of defining user roles and security authorization.

Development efforts to support more cloud native capabilities

Couchbase is now working on operator support for the Open Service Broker API which provides Services catalogue Functionality. With the service catalog approach, it will be possible for a developer to access an organization’s service portal, click on Couchbase and automatically create a cluster.

“Customers have requested support for the Open Service Broker API so that within their organization they can set up a dashboard where they publish all of their services,” said Kumar.

Source link