DBMS > Apache Drill vs. JaguarDB vs. Netezza vs. Snowflake vs. VoltDB

System Properties Comparison Apache Drill vs. JaguarDB vs. Netezza vs. Snowflake vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

Performant, highly scalable DBMS for AI and IoT applications

Data warehouse and analytics appliance part of IBM PureSystems

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Relational DBMS

Key-value store
Vector DBMS

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	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

drill.apache.org

www.jaguardb.com

www.ibm.com/products/netezza

www.snowflake.com

www.voltdb.com

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Apache Software Foundation

DataJaguar, Inc.

IBM

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2012

2015

2000

2014

2010

Current release

1.20.3, January 2023

3.3 July 2023

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux
OS X
Windows

Linux

included in appliance

hosted

Linux
OS X

for development

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++

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

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Java

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

Depending on the underlying data source

yes

Snapshots and command logging

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

User concepts

Access control

Depending on the underlying data source

rights management via user accounts

Users with fine-grained authorization concept

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

Users and roles with access to stored procedures

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.