DBMS > Ehcache vs. Microsoft Access vs. Oracle Berkeley DB vs. SAP HANA

System Properties Comparison Ehcache vs. Microsoft Access vs. Oracle Berkeley DB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used in-process key-value store

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

Primary database model

Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.ehcache.org

www.microsoft.com/en-us/microsoft-365/access

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

www.sap.com/products/hana.html

Technical documentation

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

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

help.sap.com/hana

Developer

Terracotta Inc, owned by Software AG

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP

Initial release

2009

1992

1994

2010

Current release

3.10.0, March 2022

1902 (16.0.11328.20222), March 2019

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

Open Source

commercial license 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

Java

C++

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

Server operating systems

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Appliance or cloud-service

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JCache

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

Java

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

but no files for transaction logging

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

a simple user-level security was built in till version Access 2003

yes

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.