DBMS > Oracle Berkeley DB vs. OrigoDB vs. Rockset vs. SAP HANA

System Properties Comparison Oracle Berkeley DB vs. OrigoDB vs. Rockset vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

A fully ACID in-memory object graph database

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Object oriented DBMS

Document store

Relational DBMS

Secondary database models

Relational DBMS
Search engine

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.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

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

origodb.com

rockset.com

www.sap.com/products/hana.html

Technical documentation

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

origodb.com/docs

docs.rockset.com

help.sap.com/hana

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Robert Friberg et al

Rockset

SAP

Initial release

1994

2009

under the name LiveDB

2019

2010

Current release

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

commercial license available

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

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

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

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

dynamic typing

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

can be achieved using .NET

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

Read-only SQL queries, including JOINs

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP REST

JDBC
ODBC

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

.Net

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

only for the SQL API

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

Access rights for users and organizations can be defined via Rockset console

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.