DBMS > GigaSpaces vs. KairosDB vs. Kinetica vs. Snowflake vs. ToroDB

System Properties Comparison GigaSpaces vs. KairosDB vs. Kinetica vs. Snowflake vs. ToroDB

Editorial information provided by DB-Engines

Name

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

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Distributed Time Series DBMS based on Cassandra or H2

Fully vectorized database across both GPUs and CPUs

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

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

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Relational DBMS

Document store

Secondary database models

Graph DBMS
Search engine

Spatial DBMS
Time Series DBMS

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

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.gigaspaces.com

github.com/kairosdb/kairosdb

www.kinetica.com

www.snowflake.com

github.com/torodb/server

Technical documentation

docs.gigaspaces.com/latest/landing.html

kairosdb.github.io

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

Gigaspaces Technologies

Kinetica

Snowflake Computing Inc.

8Kdata

Initial release

2000

2013

2012

2014

2016

Current release

15.5, September 2020

1.2.2, November 2018

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

Open Source

Apache 2.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

Java

C, C++

Java

Server operating systems

Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Linux

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

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

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

SQL-like DML and DDL statements

yes

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C++
Java
Python
Scala

Java
JavaScript

Node.js
PHP
Python

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes, event driven architecture

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

based on Cassandra

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

selectable replication factor

based on Cassandra

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency or Eventual Consistency depending on configuration

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

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

Role-based access control

simple password-based access control

Access rights for users and roles on table level

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

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.