Multi-model database: Difference between revisions

Revision as of 14:43, 12 August 2022

Revision as of 05:53, 18 August 2022

Line 37:

== Benchmarking multi-model databases ==

As more and more platforms are proposed to deal with multi-model data, there are a few works on benchmarking multi-model databases. For instance, Pluciennik,<ref>{{Cite journal|last=Ewa Pluciennik and Kamil Zgorzalek|title=The Multi-model Databases - A Review|journal=Bdas 2017|pages=141–152}}</ref> Oliveira,<ref>{{Cite journal|last=Fábio Roberto Oliveira, Luis del Val Cura|title=Performance Evaluation of NoSQL Multi-Model Data Stores in Polyglot Persistence Applications|journal=Ideas '16|pages=230–235}}</ref> and UniBench<ref>{{Cite journal|last=Chao Zhang, Jiaheng Lu, Pengfei Xu, Yuxing Chen|title=UniBench: A Benchmark for Multi-Model Database Management Systems|url=https://www.cs.helsinki.fi/u/jilu/documents/UniBench.pdf|journal=TPCTC 2018}}</ref> reviewed existing multi-model databases and made an evaluation effort towards comparing multi-model databases and other SQL and NoSQL databases respectively. They pointed out that the advantages of multi-model databases over single-model databases are as follows : (i){{olist|list-style-type=lower-roman| they are able to ingest a variety of data formats such as CSV( (including Graph, Relational), JSON into storage without any additional efforts,. (ii)| they can employ a unified query language such as AQL, Orient SQL, SQL/XML, SQL/JSON to retrieve correlated multi-model data, such as graph-JSON-key/value, XML-relational, and JSON-relational in a single platform. (iii)| they are able to support multi-model ACID transactions in the stand-alone mode.}}

== Architecture ==