openstack trove and dbaas api: impedance match? by fred dalrymple

© 2014 EnterpriseDB Corporation. All rights reserved. 1

OpenStack Trove and DBaaS: Impedance Match?June 11, 2015


• Fred Dalrymple− EDB, product manager, Postgres Plus Cloud Database− Representing one database provider’s perspective of Trove− http://www.enterprisedb.com− @enterprisedb− @fred_dalrymple

• Amrith Kumar− Tesora, Founder and CTO− Representing Trove’s perspective− http://www.tesora.com− @tesoracorp− @amrithkumar

Introduction

http://www.enterprisedb.com/

http://www.tesora.com/

http://www.tesora.com/


• Trove is an open source project providing a consistent API and functionality for provisioning SQL and NoSQL databases

• Applications connect directly to the database, Trove is not in the data path

• Trove orchestrates cloud and database cluster functionality, such as− Scale up instances− Create replicas− Perform backups

About OpenStack Trove


• Postgres Plus Cloud Database [PPCD]: − Deploys clusters of Postgres databases− Provides provisioning and cloud scalability− Offers a RESTful management API− These characteristics are shared with Trove, but EDB

considers them product differentiators and customer benefits

• PPCD is available on OpenStack and on Amazon Web Services (with more cloud providers to come)

About EDB Postgres Plus Cloud Database


• Still maturing, particularly for cloud scaling capabilities

• Trove is only available for OpenStack and doesn’t (yet) solve the bigger management challenge:− Enterprises need to manage all deployment choices, including

hybrid and public clouds from different providers

• Trove functionality overlaps DBaaS solutions that are already cloudified

Trove Weaknesses – EDB Perspective


• Trove scales to different databases in one cloud platform, while PPCD scales to different cloud platforms

• The customer benefits of PPCD’s better provisioning and cloud functionality are− Either hidden by Trove’s current implementation (will change in

the longer term)− Or EDB must perform significant work to preserve our

customer benefits within a Trove-compatible approach (whatever that means)

• At the same time, Trove increases the time-to-market, and competition, from databases not yet “cloudified”

EnterpriseDB Perspective


• Enterprises use many databases, some SQL, some NoSQL− Trove supports PostgreSQL, MySQL, Vertica, DB2, MongoDB,

Cassandra, Couchbase, Redis, …− Tesora’s Trove also supports Oracle and soon SQL Server

• A common set of API’s for all databases is very valuable to users and ops

• Trove is in production at scale; publicly announced users include HP, Rackspace, eBay. Several financial services companies too!

Tesora’s Perspective


• Tesora and EDB have a joint customer!

• Tesora is (working with EnterpriseDB) adding PPAS support to Trove including− Replication and Failover, Clustering, Backup and Restore,

Scale up and scale down− Things that Trove already does for many databases!

• If you use exactly one database in your company (but many clouds), PPCD is a much better answer− But if you use more than one database, and are using

OpenStack, the benefits of Trove are enormous

Tesora’s Perspective


• Given technology overlaps between PPCD and Trove...

• Which path should we take?

− Conform to Trove, but don’t expose important features?

− Extend Trove, but do it unilaterally?

− Offer the PPCD management API instead (and not provide API interoperability with Trove)?

− Eliminate PPCD native cloud functionality in favor of Trove?

− Generalize PPCD to become a Trove implementation?

EnterpriseDB Choices


Discussion and Questions

openstack trove and dbaas api: impedance match? by fred dalrymple

Technology