*Result*: A proposal of architecture for integration and uniform use of hybrid SQL/NoSQL database components.

Title:
A proposal of architecture for integration and uniform use of hybrid SQL/NoSQL database components.
Authors:
Bjeladinovic, Srdja1 (AUTHOR) srdja.bjeladinovic@fon.bg.ac.rs, Marjanovic, Zoran1 (AUTHOR) zoran.marjanovic@fon.bg.ac.rs, Babarogic, Sladjan1 (AUTHOR) sladjan.babarogic@fon.bg.ac.rs
Source:
Journal of Systems & Software. Oct2020, Vol. 168, pN.PAG-N.PAG. 1p.
Database:
Business Source Premier

*Further Information*

*The popularity of social networks and the expansion of various second-generation Internet services have contributed to the increase of data, of different structuredness levels, in use. Relational databases (frequently called SQL databases) pose themselves as a logical choice for the management of data containing fixed or rarely changeable structure. The need for fast processing of vast quantities of unstructured data has opened the door for the rise of NoSQL databases popularity. The business of modern organizations often faces the challenge of parallel use of different database types. In recent years, hybrid SQL/NoSQL databases, which contain SQL and NoSQL databases as its components, become a popular solution for the issue above. This paper identifies and describes a possible way of integration and uniform use (as two significant non-functional requirements) of hybrid database components, as well as introduce the architecture for this purpose. The presented architecture, with its specially developed components, provides as simple usage as a single database does, with advantages of parallel use of databases of different types. The functioning principle of the new architecture is elaborated on a series of practical use cases of various complexities, which were tested against a hybrid database, and Oracle and MongoDB as well. • SQL and NoSQL databases are popular and efficient, each for its own purpose. • Hybrid databases use different type databases (SQL and NoSQL) as its components. • SQL and mappings rules can be used for uniform use of hybrid database components. • Expansion of three-tier architecture allows integration of hybrid database components. [ABSTRACT FROM AUTHOR]

Copyright of Journal of Systems & Software is the property of Elsevier B.V. and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)*