DBMS > Apache Drill vs. Apache Phoenix vs. HBase vs. SQLite vs. TempoIQ

System Properties Comparison Apache Drill vs. Apache Phoenix vs. HBase vs. SQLite vs. TempoIQ

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 scale-out RDBMS with evolutionary schema built on Apache HBase

Wide-column store based on Apache Hadoop and on concepts of BigTable

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store
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.97
Rank	#126	Overall
	#59	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

tempoiq.com (offline)

Technical documentation

drill.apache.org/docs

phoenix.apache.org

hbase.apache.org/book.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Dwayne Richard Hipp

TempoIQ

Initial release

2012

2014

2008

2000

2012

Current release

1.20.3, January 2023

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

2.3.4, January 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

Apache version 2

Open Source

Public Domain

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

Java

Server operating systems

Linux
OS X
Windows

Linux
Unix
Windows

using Cygwin

server-less

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

schema-free, schema definition possible

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

Java API
RESTful HTTP API
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

C++

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.