DBMS > GridGain vs. Snowflake vs. TerminusDB vs. TimescaleDB

System Properties Comparison GridGain vs. Snowflake vs. TerminusDB vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

Time Series DBMS

Secondary database models

Document store
RDF store

Relational DBMS

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	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

docs.timescale.com

Developer

GridGain Systems, Inc.

Snowflake Computing Inc.

DataChemist Ltd.

Timescale

Initial release

2007

2014

2018

2017

Current release

GridGain 8.5.1

11.0.0, January 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

Apache 2.0

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

Prolog, Rust

Server operating systems

Linux
OS X
Solaris
Windows

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

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

yes

SQL-like query language (WOQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

JavaScript
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

user defined functions

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Journaling Streams

Source-replica replication with hot standby and reads on replicas

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

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 journaling

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

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

Role-based access control

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.