DBMS > Heroic vs. Immudb vs. Oracle Berkeley DB vs. Trafodion

System Properties Comparison Heroic vs. Immudb vs. Oracle Berkeley DB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used in-process key-value store

Transactional SQL-on-Hadoop DBMS

Primary database model

Time Series 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

Relational DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.24
Rank	#295	Overall
	#42	Key-value stores

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Website

github.com/spotify/heroic

github.com/codenotary/immudb
immudb.io

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

trafodion.apache.org

Technical documentation

spotify.github.io/heroic

docs.immudb.io

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

trafodion.apache.org/documentation.html

Developer

Spotify

Codenotary

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation, originally developed by HP

Initial release

2014

2020

1994

2014

Current release

1.2.3, April 2022

18.1.40, May 2020

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

commercial license available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

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

C++, Java

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like syntax

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

.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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

In-memory capabilities

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

yes

User concepts

Access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

A Step by Step Guide to immudb — the open source immutable database
18 May 2020, hackernoon.com

immudb (immutable database) ‘tamper-proof’ database
14 December 2021, ComputerWeekly.com

ImmuDB and Codenotary: It's a database, but the company isn't
20 December 2021, ZDNet

Immudb: Open-source database, built on a zero trust model
17 December 2021, Help Net Security

How Open-Source Database immudb Plans to Handle All That Metaverse Data
10 October 2022, Acceleration Economy

provided by Google News

What is NoSQL (Not Only SQL database)?
28 February 2022, TechTarget

Margo I. Seltzer
18 August 2020, Berkman Klein Center

Oracle acquires Sleepycat for code
17 August 2016, East Bay Times

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular
5 March 2019, ADT Magazine

How to store financial market data for backtesting
26 January 2019, Towards Data Science

provided by Google News

Share this page