DBMS > Datomic vs. Drizzle vs. EXASOL vs. NuoDB vs. Snowflake

System Properties Comparison Datomic vs. Drizzle vs. EXASOL vs. NuoDB 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.

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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.

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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

Primary database model

Relational DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.datomic.com

www.exasol.com

www.3ds.com/nuodb-distributed-sql-database

www.snowflake.com

Technical documentation

docs.datomic.com

www.exasol.com/resources

doc.nuodb.com

docs.snowflake.net/manuals/index.html

Developer

Cognitect

Drizzle project, originally started by Brian Aker

Exasol

Dassault Systèmes

originally NuoDB, Inc.

Snowflake Computing Inc.

Initial release

2012

2008

2000

2013

2014

Current release

1.0.6735, June 2023

7.2.4, September 2012

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU GPL

commercial

limited edition free

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

Java, Clojure

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

hosted

Data scheme

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

APIs and other access methods

RESTful HTTP API

JDBC

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
Java

C
C++
Java
PHP

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Java, SQL

user defined functions

Triggers

By using transaction functions

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

none

But extensive use of caching in the application peers

Sharding

data is dynamically stored/cached on the nodes where it is read/written

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

yes

Managed transparently by NuoDB

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

Temporary table

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Standard SQL roles/ privileges, Administrative Users

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.