DBMS > GeoMesa vs. HugeGraph vs. Ingres vs. MySQL vs. TerarkDB

System Properties Comparison GeoMesa vs. HugeGraph vs. Ingres vs. MySQL vs. TerarkDB

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

Well established RDBMS

Widely used open source RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Spatial DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

www.actian.com/databases/ingres

www.mysql.com

github.com/bytedance/terarkdb

Technical documentation

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

hugegraph.apache.org/docs

docs.actian.com/ingres

dev.mysql.com/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

CCRi and others

Baidu

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

ByteDance, originally Terark

Initial release

2014

2018

1974

originally developed at University Berkely in early 1970s

1995

2016

Current release

5.0.0, May 2024

0.9

11.2, May 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted open source version 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

Java

C and C++

C++

Server operating systems

Linux
macOS
Unix

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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.

but tools for importing/exporting data from/to XML-files available

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

Groovy
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

proprietary syntax

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

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

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

Ingres Replicator

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.