DBMS > GeoMesa vs. HugeGraph vs. Ultipa

System Properties Comparison GeoMesa vs. HugeGraph vs. Ultipa

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

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Spatial DBMS

Graph DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	0.13
Rank	#335	Overall
	#31	Graph DBMS

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

www.ultipa.com

Technical documentation

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

hugegraph.apache.org/docs

www.ultipa.com/document

Developer

CCRi and others

Baidu

Ultipa

Initial release

2014

2018

2019

Current release

4.0.5, February 2024

0.9

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

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

Server operating systems

Linux
macOS
Unix

Data scheme

yes

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.

Secondary indexes

yes

also supports composite index and range index

SQL

Support of SQL

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

RESTful HTTP API

Supported programming languages

Groovy
Java
Python

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Triggers

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

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

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

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

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

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Critical Apache HugeGraph Flaw Let Attackers Execute Remote Code
23 April 2024, GBHackers

provided by Google News

Technology
7 March 2024, Caj News Africa

provided by Google News

Share this page