DBMS > Apache Drill vs. BigObject vs. Snowflake vs. SQL.JS vs. Tibero

System Properties Comparison Apache Drill vs. BigObject vs. Snowflake vs. SQL.JS vs. Tibero

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for real-time computations and queries

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

Port of SQLite to JavaScript

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Relational DBMS

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.53
Rank	#246	Overall
	#115	Relational DBMS

Score	1.46
Rank	#151	Overall
	#70	Relational DBMS

Website

us.tmaxsoft.com/products/tibero

Technical documentation

drill.apache.org/docs

docs.bigobject.io

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Apache Software Foundation

BigObject, Inc.

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

TmaxSoft

Initial release

2012

2015

2014

2012

2003

Current release

1.20.3, January 2023

7, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free community edition available

commercial

Open Source

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

JavaScript

C and Assembler

Server operating systems

Linux
OS X
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

server-less, requires a JavaScript environment (browser, Node.js)

AIX
HP-UX
Linux
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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

fluentd
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C++

JavaScript (Node.js)
Python

JavaScript

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

Lua

user defined functions

Persistent Stored Procedure (PSM)

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

except by serializing a db to a file

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

planned for next version

User concepts

Access control

Depending on the underlying data source

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.