Managing Schema Evolution in NoSQL Data Stores
Stefanie Scherzinger, Meike Klettke
Abstract
Stefanie Scherzinger, Meike Klettke
Abstract
NoSQL data stores are commonly schema-less, providing no means for globally defining or managing the schema. While this offers great flexibility in early stages of application development, devel-opers soon can experience the heavy burden of dealing with in-creasingly heterogeneous data. This paper targets schema evolution for NoSQL data stores, the complex task of adapting and chang-ing the implicit structure of the data stored. We discuss the re-commendations of the developer community on handling schema changes, and introduce a simple, declarative schema evolution lan-guage. With our language, software developers and architects can systematically manage the evolution of their production data and perform typical schema maintenance tasks. We further provide a holistic NoSQL database programming language to define the se-mantics of our schema evolution language. Our solution does not require any modifications to the NoSQL data store, treating the data store as a black box. Thus, we want to address application develop-ers that use NoSQL systems as database-as-a-service.
OpenAlex reports 17 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
NoSQL data stores are commonly schema-less, providing no means for globally defining or managing the schema. While this offers great flexibility in early stages of application development, devel-opers soon can experience the heavy burden of dealing with in-creasingly heterogeneous data. This paper targets schema evolution for NoSQL data stores, the complex task of adapting and chang-ing the implicit structure of the data stored. We discuss the re-commendations of the developer community on handling schema changes, and introduce a simple, declarative schema evolution lan-guage. With our language, software developers and architects can systematically manage the evolution of their production data and perform typical schema maintenance tasks. We further provide a holistic NoSQL database programming language to define the se-mantics of our schema evolution language. Our solution does not require any modifications to the NoSQL data store, treating the data store as a black box. Thus, we want to address application develop-ers that use NoSQL systems as database-as-a-service.
Key concepts: NoSQL, Computer science, Schema evolution, Schema (genetic algorithms), Database schema, Conceptual schema, Database, Schema migration