DBMS > Apache Drill vs. Blueflood vs. FatDB vs. Oracle

System Properties Comparison Apache Drill vs. Blueflood vs. FatDB vs. Oracle

Please select another system to include it in the comparison.

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.

Description

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

Scalable TimeSeries DBMS based on Cassandra

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

Widely used RDBMS

Primary database model

Document store
Relational DBMS

Time Series DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

drill.apache.org

blueflood.io

www.oracle.com/database

Technical documentation

drill.apache.org/docs

github.com/rax-maas/blueflood/wiki

docs.oracle.com/en/database

Developer

Apache Software Foundation

Rackspace

FatCloud

Oracle

Initial release

2012

2013

2012

1980

Current release

1.20.3, January 2023

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

predefined scheme

schema-free

yes

Schemaless in JSON and XML columns

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

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HTTP REST

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C++

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

via applications

PL/SQL

also stored procedures in Java possible

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Depending on the underlying data source

Can implement custom security layer via applications

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.