DBMS > AgensGraph vs. GridGain vs. IBM Db2 Event Store vs. Snowflake

System Properties Comparison AgensGraph vs. GridGain vs. IBM Db2 Event Store vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

Distributed Event Store optimized for Internet of Things use cases

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

Primary database model

Graph DBMS
Relational DBMS

Key-value store
Relational DBMS

Event Store
Time Series DBMS

Relational DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

bitnine.net/agensgraph

www.gridgain.com

www.ibm.com/products/db2-event-store

www.snowflake.com

Technical documentation

bitnine.net/documentation

www.gridgain.com/docs/index.html

www.ibm.com/docs/en/db2-event-store

docs.snowflake.net/manuals/index.html

Developer

Bitnine Global Inc.

GridGain Systems, Inc.

IBM

Snowflake Computing Inc.

Initial release

2016

2007

2017

2014

Current release

2.1, December 2018

GridGain 8.5.1

2.0

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free developer edition available

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

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Linux

Linux, macOS, Windows for the developer addition

hosted

Data scheme

depending on used data model

yes

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

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

yes

SQL

Support of SQL

yes

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

yes

through the embedded Spark runtime

yes

APIs and other access methods

Cypher Query Language
JDBC

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

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

yes

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

Active-active shard replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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

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.