NoSQL database developer Couchbase on Aug. 30 launched something that Docker/microservices/container-deployment developers may find rather intriguing: the first NoSQL autonomous operator for Kubernetes.
The Mountain View, Calif.-based company, which also makes what it terms the “world’s first engagement database” focused on UX (user experience), described Autonomous Operator for Kubernetes is an application-specific controller that automates the management of shell scripts, reduces complexity and human error and automates manual management of database services.
Naturally, Couchbase claims this will result in streamlined operations, more efficient consumption of resources and cloud portability. In theory, yes; it may work that way for you, it may not. Checking it out is probably a good idea.
Extends Kubernetes API to Manage Complex Instances
Couchbase Autonomous Operator extends the Kubernetes application programming interface (API) to create, configure and manage instances of complex stateful applications on behalf of a Kubernetes user. It builds upon the basic Kubernetes resource and controller concepts, Couchbase said, but also includes domain or application-specific knowledge to automate common tasks better managed by pre-stated policies.
It doesn’t matter whether an enterprise is using a single provider, a hybrid cloud or cross-cloud strategy, the Autonomous Operator is deployment-agnostic, thereby enabling multi-cloud deployment and migration, the company said.
The use of Kubernetes and containers continue to gain momentum; no question about that, because IT organizations increasingly are adopting cloud computing and embracing newer technologies such as microservices, mobile, IoT and others. However, Couchbase said it has identified the following key roadblocks that hinder progress:
- High operational costs: Manually deploying and managing hundreds of database instances across multiple geographies increases cost, effort and complexity.
- Vendor lock-in: A lack of standardization to ensure data can be moved freely and safely between cloud providers has made it difficult to switch providers quickly or work with multiple providers.
- Delayed time to market: Customers with applications using microservice architectures have difficulties managing and scaling database clusters in siloed systems, extending development times and making it harder to support their applications.
The Autonomous Operator for Kubernetes was built to address and overcome these challenges for the enterprise by providing:
- Automated operations: Beta users report reductions of up to 95 percent of the operational complexity, which lowers operational costs.
- Cloud-agnostic deployment and management: Offers enterprise customers with multi-cloud strategies the ability to deploy, manage and move their applications to and from any cloud, at any time.
- Agility and flexibility: Allows customers who have adopted microservice architectures to run their database next to their application, reducing the DevOps cycle and decreasing time to market.
Couchbase and Red Hat are partnering to bring the Operator framework to applications, such as the Couchbase Data Platform, into the market.
“Our joint customers will benefit from adopting Couchbase’s distributed NoSQL database on OpenShift to provide application portability across hybrid and multi-cloud environments while increasing performance, agility and availability,” Jack Baratta, Red Hat Senior Director of Global ISVs and Alliances, said in a media advisory. “The Red Hat OpenShift Container Platform is a strategic deployment platform for the Couchbase Autonomous Operator, which is certified and available in the Red Hat Container Catalog registry this week.”
For more information, go here.