DBMS > Drizzle vs. EsgynDB vs. H2 vs. Snowflake vs. Splunk

System Properties Comparison Drizzle vs. EsgynDB vs. H2 vs. Snowflake vs. Splunk

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.

Description

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Analytics Platform for Big Data

Primary database model

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

Technical documentation

www.h2database.com/html/main.html

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Drizzle project, originally started by Brian Aker

Esgyn

Thomas Mueller

Snowflake Computing Inc.

Splunk Inc.

Initial release

2008

2015

2005

2014

2003

Current release

7.2.4, September 2012

2.2.220, July 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Limited free edition and free developer edition 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++

C++, Java

Java

Server operating systems

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

hosted

Linux
OS X
Solaris
Windows

Data scheme

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

SQL

Support of SQL

yes

with proprietary extensions

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

Java

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

Java Stored Procedures and User-Defined Functions

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

Multi-source 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

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

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.