DBMS > Drizzle vs. Riak KV vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Drizzle vs. Riak KV vs. SAP Advantage Database Server vs. Snowflake

Please select another system to include it in the comparison.

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.

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Distributed, fault tolerant key-value store

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

OpenSource, formerly Basho Technologies

Sybase, SAP

Snowflake Computing Inc.

Initial release

2008

2009

1993

2014

Current release

7.2.4, September 2012

3.2.0, December 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

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

restricted

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

HTTP API
Native Erlang Interface

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
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

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

yes

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets 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.

caching of (temporary) tables can be configured

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes, using Riak Security

fine grained access rights according to SQL-standard

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.