DBMS > Apache Drill vs. FatDB vs. RethinkDB vs. Snowflake vs. Trafodion

System Properties Comparison Apache Drill vs. FatDB vs. RethinkDB vs. Snowflake vs. Trafodion

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Spatial 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	2.74
Rank	#105	Overall
	#19	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

rethinkdb.com/docs

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

FatCloud

The Linux Foundation

since July 2017

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2012

2009

2014

Current release

1.20.3, January 2023

2.4.1, August 2020

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

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

C++, Java

Server operating systems

Linux
OS X
Windows

Windows

Linux
OS X
Windows

hosted

Linux

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

string, binary, float, bool, date, geometry

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

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

C++

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

Java Stored Procedures

Triggers

yes

via applications

Client-side triggers through changefeeds

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

User concepts

Access control

Depending on the underlying data source

Can implement custom security layer via applications

yes

users and table-level permissions

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

fine grained access rights according to SQL-standard

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.