DBMS > ArangoDB vs. H2GIS vs. Virtuoso

System Properties Comparison ArangoDB vs. H2GIS vs. Virtuoso

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native multi-model DBMS for graph, document, key/value and search. All in one engine and accessible with one query language.

Spatial extension of H2

Virtuoso is a multi-model hybrid-RDBMS that supports management of data represented as relational tables and/or property graphs

Primary database model

Document store
Graph DBMS
Key-value store
Search engine

Spatial DBMS

Document store
Graph DBMS
Native XML DBMS
Relational DBMS
RDF store
Search engine

Secondary database models

Relational DBMS

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.87
Rank	#88	Overall
	#15	Document stores
	#5	Graph DBMS
	#13	Key-value stores
	#10	Search engines

Score	0.04
Rank	#367	Overall
	#7	Spatial DBMS

Score	3.20
Rank	#80	Overall
	#14	Document stores
	#4	Graph DBMS
	#2	Native XML DBMS
	#44	Relational DBMS
	#2	RDF stores
	#9	Search engines

Website

arangodb.com

www.h2gis.org

virtuoso.openlinksw.com

Technical documentation

docs.arangodb.com

www.h2gis.org/docs/home

docs.openlinksw.com/virtuoso

Developer

ArangoDB Inc.

CNRS

OpenLink Software

Initial release

2012

2013

1998

Current release

3.11.5, November 2023

7.2.11, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial license (Enterprise) available

Open Source

LGPL 3.0

Open Source

GPLv2, extended commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

automatically recognizes schema within a collection

yes

SQL - Standard relational schema
RDF - Quad (S, P, O, G) or Triple (S, P, O)
XML - DTD, XML Schema
DAV - freeform filesystem objects, plus User Defined Types a/k/a Dynamic Extension Type

Typing

predefined data types such as float or date

yes

string, double, boolean, list, hash

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92, SQL-200x, SQL-3, SQLX

APIs and other access methods

AQL
Foxx Framework
Graph API (Gremlin)
GraphQL query language
HTTP API
Java & SpringData
JSON style queries
VelocyPack/VelocyStream

ADO.NET
GeoSPARQL
HTTP API
JDBC
Jena RDF API
ODBC
OLE DB
RDF4J API
RESTful HTTP API
Sesame REST HTTP Protocol
SOAP webservices
SPARQL 1.1
WebDAV
XPath
XQuery
XSLT

Supported programming languages

C#
C++
Clojure
Elixir
Go
Java
JavaScript (Node.js)
PHP
Python
R
Rust

Java

.Net
C
C#
C++
Java
JavaScript
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

JavaScript

yes

based on H2

yes

Virtuoso PL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

since version 2.0

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with configurable replication factor

yes

based on H2

Chain, star, and bi-directional replication
Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be done with stored procedures in JavaScript

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

configurable per collection or per write
Immediate Consistency
OneShard (highly available, fault-tolerant deployment mode with ACID semantics)

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes

based on H2

Fine-grained Attribute-Based Access Control (ABAC) in addition to typical coarse-grained Role-Based Access Control (RBAC) according to SQL-standard. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

The Weight of Relational Databases: Time for Multi-Model?
29 August 2017, Luca Olivari (guest author)

show all

Share this page