DBMS > Apache Drill vs. Drizzle vs. Geode vs. Snowflake

System Properties Comparison Apache Drill vs. Drizzle vs. Geode 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.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

geode.apache.org

www.snowflake.com

Technical documentation

drill.apache.org/docs

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Snowflake Computing Inc.

Initial release

2012

2008

2002

2014

Current release

1.20.3, January 2023

7.2.4, September 2012

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Linux
OS X
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

schema-free

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C++

C
C++
Java
PHP

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

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.