DBMS > CrateDB vs. Drizzle vs. JaguarDB vs. Snowflake

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

Distributed Database based on Lucene

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

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.73
Rank	#224	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#8	Vector DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cratedb.com

www.jaguardb.com

www.snowflake.com

Technical documentation

cratedb.com/docs

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Crate

Drizzle project, originally started by Brian Aker

DataJaguar, Inc.

Snowflake Computing Inc.

Initial release

2013

2008

2015

2014

Current release

7.2.4, September 2012

3.3 July 2023

License

Commercial or Open Source

Open Source

GNU GPL

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.

CrateDB Cloud: a distributed SQL database that spreads data and processing across an elastic cluster of shared nothing nodes. CrateDB Cloud enables data insights at scale on Microsoft Azure, AWS and Google Cloud Platform.

Implementation language

Java

C++

the server part. Clients available in other languages

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

FreeBSD
Linux
OS X

Linux

hosted

Data scheme

Flexible Schema (defined schema, partial schema, 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, but no triggers and constraints, and PostgreSQL compatibility

yes

with proprietary extensions

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

JDBC

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

C
C++
Java
PHP

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions (Javascript)

user defined functions

Triggers

hooks for callbacks inside the server can be used.

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

Configurable replication on table/partition-level

Multi-source replication
Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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.

User concepts

Access control

rights management via user accounts

Pluggable authentication mechanisms

e.g. LDAP, HTTP

rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

Specific characteristics

The enterprise database for time series, documents, and vectors. Distributed - Native...
» more

Competitive advantages

Response time in milliseconds: e ven for complex ad-hoc queries. Massive scaling...
» more

Typical application scenarios

IoT: accelerate your IIoT projects with CrateDB, delivering real-time analytics...
» more

Key customers

Across all continents, CrateDB is used by companies of all sizes to meet the most...
» more

Market metrics

The CrateDB open source project was started in 2013 Honorable Mention in 2021 Gartner®...
» more

Licensing and pricing models

See CrateDB pricing >
» more

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.