DBMS > Apache Drill vs. jBASE vs. MySQL vs. TempoIQ

System Properties Comparison Apache Drill vs. jBASE vs. MySQL vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

A robust multi-value DBMS comprising development tools and middleware

Widely used open source RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Relational DBMS

Multivalue DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

drill.apache.org

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

www.mysql.com

tempoiq.com (offline)

Technical documentation

drill.apache.org/docs

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

dev.mysql.com/doc

Developer

Apache Software Foundation

Rocket Software (formerly Zumasys)

Oracle

since 2010, originally MySQL AB, then Sun

TempoIQ

Initial release

2012

1991

1995

2012

Current release

1.20.3, January 2023

5.7

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Server operating systems

Linux
OS X
Windows

AIX
Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

C++

.Net
Basic
Jabbascript
Java

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

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

no user groups or roles

simple authentication-based access control

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.