DBMS > GeoMesa vs. HugeGraph vs. OpenQM vs. Oracle

System Properties Comparison GeoMesa vs. HugeGraph vs. OpenQM vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A fast-speed and highly-scalable Graph DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.oracle.com/database

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

hugegraph.apache.org/docs

docs.oracle.com/en/database

Developer

CCRi and others

Baidu

Rocket Software, originally Martin Phillips

Oracle

Initial release

2014

2018

1993

1980

Current release

5.0.0, May 2024

0.9

3.4-12

23c, September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

GPLv2, extended commercial license available

commercial

restricted free version is 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

Scala

Java

C and C++

Server operating systems

Linux
macOS
Unix

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

with some exceptions

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

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

also supports composite index and range index

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Groovy
Java
Python

.Net
Basic
C
Java
Objective C
PHP
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

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.

depending on storage layer

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.