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

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store
Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Search engine

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

drill.apache.org

www.jaguardb.com

www.ibm.com/products/netezza

www.snowflake.com

sphinxsearch.com

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Apache Software Foundation

DataJaguar, Inc.

IBM

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2012

2015

2000

2014

2001

Current release

1.20.3, January 2023

3.3 July 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

Linux
OS X
Windows

Linux

included in appliance

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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

full-text index on all search fields

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

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Proprietary protocol

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

none

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

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

Depending on the underlying data source

yes

The original contents of fields are not stored in the Sphinx index.

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

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.