New cardinality notations and styles for modeling NoSQL document-store databases

Abstract

Nowadays, data with several characteristics such as volume, variety etc. are generated daily, i.e. big data; its complexity cannot be overemphasized. On the other hand, schema free NoSQL databases keep emerging at almost the same phase to accommodate such data which cannot be efficiently managed by relational databases. However, this advancement brings about the challenge to model such flexible databases and capably manage big data despite its complexity. In doing that, developers tend to apply their relational modeling skills; nonetheless, such skills may not be directly compatible with NoSQL databases due to their schema flexibility, linear scalability among others. To alleviate this difficulty, we propose a standard for modeling NoSQL databases, document-stores in particular. The standard can be classified as i) cardinality notations, and ii) relationship modeling styles. With such standard, NoSQL document-store databases can be properly designed, automated database testing can be applied, and database performance and stability can be considerably improved. To achieve this, experimental method is applied. Also, exploratory approach was used to explore the available literature as well as experts consultations. All possible entity relationships were extracted, aggregated and compiled from a heuristic evaluation of existing 4 different document-store databases. An experiment was conducted to assess the effect of the proposed standards, results indicate a profound improvements in various aspect of document modeling when the proposed standards are adopted, especially in a large scaled databases.

Automatic schema suggestion model for NoSQL document-stores databases

“…Firstly, the IS was generated through the proposed model which adopted the new cardinalities and styles [11]. The proposed model also incorporated modeling guidelines proposed in [12].…”

“…Semantic mappings of the recorded entities are then initiated by the model itself starting from third layer. This is achieved partly using modeling guidelines [12] and new generation cardinalities [11]. The following algorithms explain the logic.…”

“…The said earlier studies were motivated by the industrially proven problems, theoretically grounded with basic modeling facts, and empirically validated through repeated and rigorous experiments. One of the aforesaid studies, focuses on cardinality notations and styles [11], while the other presented modeling guidelines [12]. The two studies scoped at NoSQL document-store databases.…”

“…With the above described model, parameters together with their associated data can be supplied into the proposed model to produce initial schema based on solid theoretical and empirical foundations adopted from [11,12]. It should be unequivocally noted that, the proposed model does not produce fully functional schema which can be 100% copy-pasted, rather produce a schema with basic modeling concepts that can be used at the initial stage of database design.…”

Data Modeling Guidelines for NoSQL Document-Store Databases

“…, developer autonomy [1], [12] and inadequate modeling guidelines [13], have posed numerous challenges in NoSQL schema best-practice implementation. This has increasingly led to erroneous database modeling and designs [1], [14], [15], [16], [17], which defeats the notion of robustness in NoSQL databases and results in the production of low-performance, non-secure and less-durable systems.…”