DBMS > Apache Drill vs. jBASE vs. RRDtool vs. Snowflake

System Properties Comparison Apache Drill vs. jBASE vs. RRDtool vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A robust multi-value DBMS comprising development tools and middleware

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

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

Primary database model

Document store
Relational DBMS

Multivalue DBMS

Time Series 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	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

oss.oetiker.ch/rrdtool

www.snowflake.com

Technical documentation

drill.apache.org/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

oss.oetiker.ch/rrdtool/doc

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Rocket Software (formerly Zumasys)

Tobias Oetiker

Snowflake Computing Inc.

Initial release

2012

1991

1999

2014

Current release

1.20.3, January 2023

5.7

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux
OS X
Windows

AIX
Linux
Windows

HP-UX
Linux

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

Numeric data only

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

Exporting into and restoring from XML files possible

yes

Secondary indexes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

in-process shared library
Pipes

CLI Client
JDBC
ODBC

Supported programming languages

C++

.Net
Basic
Jabbascript
Java

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

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.