DBMS > Apache Drill vs. BigchainDB vs. Ehcache vs. SAP HANA vs. TimesTen

System Properties Comparison Apache Drill vs. BigchainDB vs. Ehcache vs. SAP HANA vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A widely adopted Java cache with tiered storage options

In-memory, column based data store. Available as appliance or cloud service

In-Memory RDBMS compatible to Oracle

Primary database model

Document store
Relational DBMS

Document store

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

drill.apache.org

www.bigchaindb.com

www.ehcache.org

www.sap.com/products/hana.html

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

Technical documentation

drill.apache.org/docs

bigchaindb.readthedocs.io/en/latest

www.ehcache.org/documentation

help.sap.com/hana

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

Terracotta Inc, owned by Software AG

SAP

Oracle, TimesTen Performance Software, HP

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

Initial release

2012

2016

2009

2010

1998

Current release

1.20.3, January 2023

3.10.0, March 2022

2.0 SPS07 (April 4, 2023), April 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Java

Server operating systems

Linux
OS X
Windows

Linux

All OS with a Java VM

Appliance or cloud-service

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

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

CLI Client
RESTful HTTP API

JCache

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C++

Go
Haskell
Java
JavaScript
Python
Ruby

Java

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

PL/SQL

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes,with MongoDB ord RethinkDB

yes

using a tiered cache-storage approach

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

yes

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.