DBMS > Apache Drill vs. MySQL vs. SWC-DB vs. TimesTen

System Properties Comparison Apache Drill vs. MySQL vs. SWC-DB vs. TimesTen

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

Widely used open source RDBMS

A high performance, scalable Wide Column DBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Wide column store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Time Series 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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

drill.apache.org

www.mysql.com

github.com/kashirin-alex/swc-db
www.swcdb.org

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

drill.apache.org/docs

dev.mysql.com/doc

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Alex Kashirin

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

1995

2020

1998

Current release

1.20.3, January 2023

8.4.0, April 2024

0.5, April 2021

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

schema-free

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

yes

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol
Thrift

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C++

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

by means of logfiles and checkpoints

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

Users with fine-grained authorization concept

no user groups or roles

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.