|
* [[AllegroGraph]] – document (JSON, JSON-LD), graph
* [[ArangoDB]] – document (JSON), graph, key-value
* [[Cosmos DB]] – document (JSON), graph,<ref>https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet</ref>, key-value, SQL
* [[Couchbase]] – document (JSON), key-value, [[N1QL]]
* [[Datastax]] – key-value, tabular, graph
== 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|first=|date=|title=The Multi-model Databases - A Review|url=|journal=BDAS 2017|volume=|pages=141-152141–152|via=}}</ref> Oliveira, Oliveira<ref>{{Cite journal|last=Fábio Roberto Oliveira, Luis del Val Cura|first=|date=|title=Performance Evaluation of NoSQL Multi-Model Data Stores in Polyglot Persistence Applications|url=|journal=IDEAS '16|volume=|pages=230-235230–235|via=}}</ref>, and UniBench<ref>{{Cite journal|last=Chao Zhang, Jiaheng Lu, Pengfei Xu, Yuxing Chen|first=|date=|title=UniBench: A Benchmark for Multi-Model Database Management Systems|url=https://www.cs.helsinki.fi/u/jilu/documents/UniBench.pdf|journal=TPCTC 2018|volume=|pages=|via=}}</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) 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 ==
|
