DBMS > Apache Drill vs. Infobright vs. NuoDB vs. SiteWhere vs. Snowflake

System Properties Comparison Apache Drill vs. Infobright vs. NuoDB vs. SiteWhere vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

M2M integration platform for persisting/querying time series data

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

drill.apache.org

ignitetech.com/softwarelibrary/infobrightdb

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

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

drill.apache.org/docs

doc.nuodb.com

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

Dassault Systèmes

originally NuoDB, Inc.

SiteWhere

Snowflake Computing Inc.

Initial release

2012

2005

2013

2010

2014

Current release

1.20.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

limited edition free

Open Source

Common Public Attribution License Version 1.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

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

predefined 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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C++

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java, SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Managed transparently by NuoDB

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Depending on the underlying data source

yes

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

yes

Temporary table

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Standard SQL roles/ privileges, Administrative Users

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.