Evolving NoSQL Databases without Downtime

NoSQL databases like Redis, Cassandra, and Mon-goDB are increasingly popular because they are flexible, lightweight, and easy to work with. Applications that use these databases will evolve over time, sometimes necessitating (or preferring) a change to the format or organization of the data. The pro...

Full description

Saved in:
Bibliographic Details
Published in2016 IEEE International Conference on Software Maintenance and Evolution (ICSME) pp. 166 - 176
Main Authors Saur, Karla, Dumitras, Tudor, Hicks, Michael
Format Conference Proceeding
LanguageEnglish
Published IEEE 01.10.2016
Subjects
Arrays
Benchmark testing
Encoding
Relational databases
Servers
Software
Online AccessGet full text

Cover

More Information
Summary:NoSQL databases like Redis, Cassandra, and Mon-goDB are increasingly popular because they are flexible, lightweight, and easy to work with. Applications that use these databases will evolve over time, sometimes necessitating (or preferring) a change to the format or organization of the data. The problem we address in this paper is: How can we support the evolution of high-availability applications and their NoSQL data online, without excessive delays or interruptions, even in the presence of backward-incompatible data format changes? We present KVolve, an extension to the popular Redis NoSQL database, as a solution to this problem. KVolve permits a developer to submit an upgrade specification that defines how to transform existing data to the newest version. This transformation is applied lazily as applications interact with the database, thus avoiding long pause times. We demonstrate that KVolve is expressive enough to support substantial practical updates, including format changes to RedisFS, a Redis-backed file system, while imposing essentially no overhead in general use and minimal pause times during updates.
DOI:10.1109/ICSME.2016.47