DBMS > GeoMesa vs. H2GIS vs. KeyDB vs. Newts vs. TinkerGraph

System Properties Comparison GeoMesa vs. H2GIS vs. KeyDB vs. Newts vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of H2

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Time Series DBMS based on Cassandra

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.geomesa.org

www.h2gis.org

github.com/Snapchat/KeyDB
keydb.dev

opennms.github.io/newts

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

www.h2gis.org/docs/home

docs.keydb.dev

github.com/OpenNMS/newts/wiki

Developer

CCRi and others

CNRS

EQ Alpha Technology Ltd.

OpenNMS Group

Initial release

2014

2013

2019

2014

2009

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

LGPL 3.0

Open Source

BSD-3

Open Source

Apache 2.0

Open Source

Apache 2.0

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++

Java

Server operating systems

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST
Java API

TinkerPop 3

Supported programming languages

Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Java

Groovy
Java

Server-side scripts

Stored procedures

yes

based on H2

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

based on H2

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

optional

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

yes

based on H2

simple password-based access control and ACL

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

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Redis 6 arrives with multithreading for faster I/O
30 April 2020, InfoWorld

provided by Google News

Farewell, Froggy: The Age of Ribbit Is Nearing an End
25 May 2013, Mother Jones

provided by Google News

Automated testing of Amazon Neptune data access with Apache TinkerPop Gremlin | Amazon Web Services
28 September 2022, AWS Blog

Simple Deployment of a Graph Database: JanusGraph | by Edward Elson Kosasih
12 October 2020, Towards Data Science

Why developers like Apache TinkerPop, an open source framework for graph computing | Amazon Web Services
27 September 2021, AWS Blog

InfiniteGraph Gets Support for Common Graph Database Language and More
21 February 2012, SiliconANGLE News

Introducing Gremlin query hints for Amazon Neptune | AWS Database Blog
26 February 2019, AWS Blog

provided by Google News

Share this page