4.4. Unique access for all data stores
4.4.1. Introduction
In some cases, applications want to explicitly store and manipulate their data in multiple data stores. Applications already know the set of data stores to use and how to distribute their data on these sources. However, in order to simplify the development process, application developers do not want to manipulate different proprietary APIs, especially when interacting with multiple data stores (e.g. relational, NoSQL, etc.). Two classes of solutions can be used in this case. The first is based on the definition of a neutral API capable of supporting access to the different data stores. The second class is based on the model-driven architecture and engineering methodology [POO 01].
In this section, we focus exclusively on the first class of solutions to ease access to multiple data stores (especially NoSQL and relational data stores). Stonebraker [STO 11] exposes the problems and the limits that a user may encounter while using...
