DBMS > Drizzle vs. Heroic vs. openGemini vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Drizzle vs. Heroic vs. openGemini vs. SAP Advantage Database Server vs. Snowflake

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

An open source distributed Time Series DBMS with high concurrency, high performance, and high scalability

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

Time Series DBMS

Relational DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.09
Rank	#361	Overall
	#37	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/spotify/heroic

www.opengemini.org
github.com/openGemini

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

www.snowflake.com

Technical documentation

spotify.github.io/heroic

docs.opengemini.org/guide

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

Spotify

Huawei and openGemini community

Sybase, SAP

Snowflake Computing Inc.

Initial release

2008

2014

2022

1993

2014

Current release

7.2.4, September 2012

1.1, July 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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

Server operating systems

FreeBSD
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

Integer, Float, Boolean, String

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

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP REST

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
JavaScript (Node.js)
Python
Rust

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate 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

caching of (temporary) tables can be configured

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Administrators and common users accounts

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.