DBMS > GridGain vs. Kinetica vs. Snowflake vs. Spark SQL vs. STSdb

System Properties Comparison GridGain vs. Kinetica vs. Snowflake vs. Spark SQL vs. STSdb

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS
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	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

www.gridgain.com/docs/index.html

docs.kinetica.com

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

GridGain Systems, Inc.

Kinetica

Snowflake Computing Inc.

Apache Software Foundation

STS Soft SC

Initial release

2007

2012

2014

2011

Current release

GridGain 8.5.1

7.1, August 2021

3.5.0 ( 2.13), September 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPLv2, commercial license available

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

Scala

Server operating systems

Linux
OS X
Solaris
Windows

Linux

hosted

Linux
OS X
Windows

Windows

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL-like DML and DDL statements

yes

SQL-like DML and DDL statements

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC

.NET Client API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Java
Python
R
Scala

C#
Java

Server-side scripts

Stored procedures

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

user defined functions

Triggers

yes (cache interceptors and events)

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

yes

none

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

Immediate Consistency or Eventual Consistency depending on configuration

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

GPU vRAM or System RAM

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles on table level

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.