DBMS > Oracle Berkeley DB vs. SAP HANA vs. TimesTen vs. Yanza

System Properties Comparison Oracle Berkeley DB vs. SAP HANA vs. TimesTen vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used in-process key-value store

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

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Time Series DBMS for IoT Applications

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Time Series 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	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

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

www.sap.com/products/hana.html

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

yanza.com

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

help.sap.com/hana

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP

Oracle

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

Yanza

Initial release

1994

2010

1998

2015

Current release

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

Release 22.1

License

Commercial or Open Source

Open Source

commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Appliance or cloud-service

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Windows

Data scheme

schema-free

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC
ODBC

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

HTTP API

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Java
Node.js
PL/SQL
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

SQLScript, R

PL/SQL

Triggers

yes

only for the SQL API

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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.