DBMS > Drizzle vs. GeoSpock vs. Riak TS vs. Snowflake vs. Yaacomo

System Properties Comparison Drizzle vs. GeoSpock vs. Riak TS vs. Snowflake vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed 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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geospock.com

www.snowflake.com

yaacomo.com

Technical documentation

www.tiot.jp/riak-docs/riak/ts/latest

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

2008

2015

2014

2009

Current release

7.2.4, September 2012

2.0, September 2019

3.0.0, September 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

commercial

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

Erlang

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux
OS X

hosted

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

yes

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

restricted

yes

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

yes, limited

yes

APIs and other access methods

JDBC

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

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.