DBMS > Drizzle vs. Hive vs. JaguarDB vs. Rockset vs. Snowflake

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

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Performant, highly scalable DBMS for AI and IoT applications

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Document store

Relational DBMS

Secondary database models

Relational DBMS
Search engine

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

Score	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

www.jaguardb.com/support.html

docs.rockset.com

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

Apache Software Foundation

initially developed by Facebook

DataJaguar, Inc.

Rockset

Snowflake Computing Inc.

Initial release

2008

2012

2015

2019

2014

Current release

7.2.4, September 2012

3.1.3, April 2022

3.3 July 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2

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++

Java

C++

the server part. Clients available in other languages

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

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

dynamic typing

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.

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Read-only SQL queries, including JOINs

yes

APIs and other access methods

JDBC

JDBC
ODBC
Thrift

JDBC
ODBC

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

C++
Java
PHP
Python

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

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Automatic 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

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles

rights management via user accounts

Access rights for users and organizations can be defined via Rockset console

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.