A Novel framework for querying multiparadigm databases

Abstract

Relational databases evolved in accordance to the prevailing technological requirements and constraints that had suitability, applicability and relevance at that time. However, times have changed and also the contemporary requirements. To alleviate the problems associated with relational databases in handling present big data, which is predominantly un-structured, a new class of databases has emerged, known as NoSQL databases. As and when a new class of data-storage emerges and becomes popular, researchers start working towards its integration with the existing databases. Likewise, with the widespread use of NoSQL data-stores, the problem of integrating them with existing database technology has became a challenge. The goal is to select the most appropriate data storage technology that meets the specific requirements of each module of the application. Amalgamation of different databases within an application is known as Multiparadigm approach or Polyglot-persistence. Persistence needs of applications are progressing from mostly relational to a mixture of data-stores. For example various modules of Health-care Information System (HIS) use different data-stores to model data closer to their semantic usage. The researcher has showcased the applicability of our multipradigm framework in HIS, considering the variety of data and diverse categories of NoSQL data-stores with which they may be managed. But the concept is equally well applicable to any other application area, where different parts of the application deals with distinct data formats. The researcher has implemented a healthcare information system PolyglotHIS, which makes use of one relational and two NoSQL data-stores. This coalition of datastores is not arbitrary, instead it is prudently chosen on the basis of careful analysis of alternative data-stores. Each involved data-store has its own specific advantage. Relational data-stores are preferred for data pertaining to financial transactions, since they support transactional properties.