DBMS > Drizzle vs. EXASOL vs. FatDB vs. JaguarDB vs. Snowflake

System Properties Comparison Drizzle vs. EXASOL vs. FatDB vs. JaguarDB 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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store
Vector DBMS

Relational DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.exasol.com

www.jaguardb.com

www.snowflake.com

Technical documentation

www.exasol.com/resources

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

Exasol

FatCloud

DataJaguar, Inc.

Snowflake Computing Inc.

Initial release

2008

2000

2012

2015

2014

Current release

7.2.4, September 2012

3.3 July 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL V3.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++

the server part. Clients available in other languages

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux

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

SQL

Support of SQL

yes

with proprietary extensions

yes

Via inetgration in SQL Server

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC

.Net
JDBC
ODBC
WebSocket

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

Java
Lua
Python
R

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

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

selectable replication factor

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual 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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles according to SQL-standard

Can implement custom security layer via applications

rights management via user accounts

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.