DBMS > GridGain vs. Rockset vs. Snowflake vs. TimescaleDB vs. XTDB

System Properties Comparison GridGain vs. Rockset vs. Snowflake vs. TimescaleDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store
Relational DBMS

Secondary database models

Relational DBMS
Search engine

Relational 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	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.gridgain.com/docs/index.html

docs.rockset.com

docs.snowflake.net/manuals/index.html

docs.timescale.com

www.xtdb.com/docs

Developer

GridGain Systems, Inc.

Rockset

Snowflake Computing Inc.

Timescale

Juxt Ltd.

Initial release

2007

2019

2014

2017

2019

Current release

GridGain 8.5.1

2.15.0, May 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

MIT License

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

Clojure

Server operating systems

Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

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

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

yes

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

yes, extensible-data-notation format

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

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

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

Read-only SQL queries, including JOINs

yes

full PostgreSQL SQL syntax

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP REST

CLI Client
JDBC
ODBC

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

HTTP REST
JDBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

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

user defined functions

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

Automatic sharding

yes

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Source-replica replication with hot standby and reads on replicas

yes, each node contains all data

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

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights for users and organizations can be defined via Rockset console

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.