DBMS > GridGain vs. JaguarDB vs. Snowflake vs. Teradata Aster vs. ToroDB

System Properties Comparison GridGain vs. JaguarDB vs. Snowflake vs. Teradata Aster vs. ToroDB

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Performant, highly scalable DBMS for AI and IoT applications

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

Platform for big data analytics on multistructured data sources and types

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store
Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Document store

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

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.gridgain.com

www.jaguardb.com

www.snowflake.com

github.com/torodb/server

Technical documentation

www.gridgain.com/docs/index.html

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

GridGain Systems, Inc.

DataJaguar, Inc.

Snowflake Computing Inc.

Teradata

8Kdata

Initial release

2007

2015

2014

2005

2016

Current release

GridGain 8.5.1

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Open Source

AGPL-V3

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

the server part. Clients available in other languages

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux

hosted

Linux

All OS with a Java 7 VM

Data scheme

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

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

JDBC
ODBC

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

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

user defined functions

R packages

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Durability

Support for making data persistent

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

Security Hooks for custom implementations

rights management via user accounts

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.