DBMS > GeoSpock vs. GridGain vs. JanusGraph vs. Snowflake vs. Yaacomo

System Properties Comparison GeoSpock vs. GridGain vs. JanusGraph vs. Snowflake vs. Yaacomo

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Spatial and temporal data processing engine for extreme data scale

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

Cloud-based data warehousing service for structured and semi-structured data

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geospock.com

www.gridgain.com

janusgraph.org

www.snowflake.com

yaacomo.com

Technical documentation

www.gridgain.com/docs/index.html

docs.janusgraph.org

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

GridGain Systems, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

2007

2017

2014

2009

Current release

2.0, September 2019

GridGain 8.5.1

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

Java, C++, .Net

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

hosted

Android
Linux
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

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

yes

APIs and other access methods

JDBC

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

user defined functions

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

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

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users can be defined per table

Security Hooks for custom implementations

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.