Let me start by explaining what we mean by “your databases, your cloud, your way.” Trove enables Database as a Service (DBaaS) for OpenStack, with the goal of allowing users to quickly and easily utilize the features of a relational or non-relational database without the burden of handling complex administrative tasks.
Trove allows IT, developers, and DevOps to administer a wide range of database technologies using a single, common management infrastructure. The result is that routine tasks like provisioning, and managing regular administrative tasks like clustering, replication, backup, and restore are handled in a simple, unified way.
This is what I’ll be talking about in my session, “Secure, Self-Service Database Management with OpenStack Database as a Service,” on Tuesday August 9 at 2:05 p.m.
Trove enables a choice of 15 different database technologies – both SQL and NoSQL datastores – and runs entirely on OpenStack. So, you are able to run your existing databases without change on your OpenStack cloud wherever you happen to choose – on-premises in your data center or from a cloud provider like Blue Box or Vexxhost. Trove supports databases for a variety of use cases from prototyping and development, to testing and QA, and production operation.
For users, OpenStack database as a service provides on-demand database capacity and self-service provisioning. For IT, Trove leverages core components and shared services of OpenStack, making it simple for enterprises to deploy DBaaS. For example, Trove uses the Nova compute service to create virtual machines on which to run database servers, Cinder block storage to provision database storage, and Swift’s object storage to capture backups. Since Trove is layered on these core services, its users can take advantage of these services without any special customization. They can also benefit from any enhancements that have been implemented in the underlying core services of OpenStack. For example, if Nova has been configured to offer bare metal resources through the OpenStack Ironic service, Trove can leverage that.
Our company is the #1 contributor to the OpenStack Trove database as a service project and we take great pride that in terms of OpenStack overall, Tesora ranks among the top 25 contributors, as measured by Stackalytics. We think that is quite a feat considering the size of the companies ahead and behind us on the list.
The most recent OpenStack Foundation survey (April 2016) shows increasing adoption and interest in Trove. It provides a good barometer of maturity, showing 3% in production and 14% in the testing phase. Trove also scored high (5th) in terms of projects that OpenStack users are most interested in (34%).
Why? A survey by 451 Research notes that when it comes to databases, enterprises are likely to have multiple suppliers for different usages. Those will include both SQL and NoSQL data stores, ones optimized for both operational and analytic workloads, as well as both open source databases and commercial database products. As these enterprises move to private, public, and hybrid cloud implementations, they bring these databases with them.
While enterprises are now using lots of databases, their management platforms have traditionally been technology specific. This trend has largely continued as database management has moved into the cloud, with single database DBaaS offerings dominating the landscape. Examples of this include Azure SQL Database (Microsoft SQL Server), MongoLab (MongoDB), and Cloudant (CouchDB). Trove takes a fundamentally different approach by creating a pluggable architecture where many different types of databases can be supported from a common infrastructure.
I’m looking forward to the OpenStack Silicon Valley event and welcome talking with you there.