DBMS > GeoMesa vs. HugeGraph vs. LevelDB vs. RavenDB

System Properties Comparison GeoMesa vs. HugeGraph vs. LevelDB vs. RavenDB

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

github.com/google/leveldb

ravendb.net

Technical documentation

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

hugegraph.apache.org/docs

github.com/google/leveldb/blob/main/doc/index.md

ravendb.net/docs

Developer

CCRi and others

Baidu

Google

Hibernating Rhinos

Initial release

2014

2018

2011

2010

Current release

4.0.5, February 2024

0.9

1.23, February 2021

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

AGPL version 3, 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

Scala

Java

C++

Server operating systems

Linux
macOS
Unix

Illumos
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
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.

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

SQL-like query language (RQL)

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

Groovy
Java
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

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

none

Sharding

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

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

Authorization levels configured per client per database

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

LevelDB in Ruby — SitePoint
22 October 2014, SitePoint

Microsoft Teams stores auth tokens as cleartext in Windows, Linux, Macs
14 September 2022, BleepingComputer

Pliops unveils XDP-Rocks for RocksDB – Blocks and Files
19 October 2022, Blocks and Files

XanMod, Liquorix Kernels Offer Some Advantages On AMD Ryzen 5 Notebook
26 July 2021, Phoronix

Rust-Based Info Stealers Abuse GitHub Codespaces
19 May 2023, Trend Micro

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page