DBMS > Drizzle vs. GeoSpock vs. Kinetica vs. Snowflake vs. TerarkDB

System Properties Comparison Drizzle vs. GeoSpock vs. Kinetica vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spatial and temporal data processing engine for extreme data scale

Fully vectorized database across both GPUs and CPUs

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

geospock.com

www.kinetica.com

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

docs.kinetica.com

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Kinetica

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2008

2012

2014

2016

Current release

7.2.4, September 2012

2.0, September 2019

7.1, August 2021

License

Commercial or Open Source

Open Source

GNU GPL

commercial

restricted open source version 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

C++

Java, Javascript

C, C++

C++

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux

hosted

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

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

temporal, categorical

yes

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

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

Automatic sharding

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

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.