DBMS > GeoMesa vs. GridGain vs. JanusGraph vs. NSDb

System Properties Comparison GeoMesa vs. GridGain vs. JanusGraph vs. NSDb

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.

GridGain is an in-memory computing platform, built on Apache Ignite

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Graph 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	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

Technical documentation

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

www.gridgain.com/docs/index.html

docs.janusgraph.org

nsdb.io/Architecture

Developer

CCRi and others

GridGain Systems, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2014

2007

2017

Current release

4.0.5, February 2024

GridGain 8.5.1

0.6.3, February 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

Open Source

Apache Version 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++, .Net

Java

Java, Scala

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

gRPC
HTTP REST
WebSocket

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

Java
Scala

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

Using Apache Lucene

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

Security Hooks for custom implementations

User authentification and security via Rexster Graph Server

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

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks & Files

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Adds Andy Sacks as Chief Revenue Officer, Promotes Lalit Ahuja to Chief Customer and Product Officer ...
17 July 2023, Yahoo Finance

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Database Deep Dives: JanusGraph
8 August 2019, ibm.com

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Compose for JanusGraph arrives on Bluemix
15 September 2017, ibm.com

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

provided by Google News

Share this page