The open-source OpenStack cloud platform includes multiple projects that can be used to enable different capabilities in the cloud. In the OpenStack Icehouse milestone release, which debuted in April 2014, a key addition was the Trove database project, which enables the use of multiple databases in an OpenStack cloud deployment.
Trove continued to be enhanced in the Juno release in October 2014 and is now set to be enhanced further in the Kilo release set for April 2015. One of the leading participants in the Trove project is Tesora, which provides a commercially supported enterprise product.
Leading Tesora is company founder and CEO Ken Rugg. In a video interview, Rugg explains what’s going on in Trove development for the Kilo release cycle. Currently there isn’t feature parity in Trove across all the different database that are supported, but that is set to be improved in 2015.
“We’re investing in the clustering for CouchDB and supporting replication features on other databases,” Rugg said.
While the idea of providing feature parity in Trove for all supported databases might sound obvious, there are some features that don’t make sense for certain databases. For example, Rugg noted that some databases do not like the idea of backups.
“Cassandra doesn’t like backups,” Rugg said. “Cassandra would rather do replication.”
The Apache Cassandra database is used for Big Data deployments. Rugg explained that in the Cassandra model, instead of doing a backup, it will just add another replica.
“The model for Trove is not to dumb everything down to the least common denominator, but to take advantage of the features that are there,” Rugg said.
Watch the full video interview with Ken Rugg, Founder and CEO of Tesora
Sean Michael Kerner is a senior editor at Datamation and InternetNews.com. Follow him on Twitter @TechJournalist
Photo courtesy of Shutterstock.