DBMS > Oracle Berkeley DB vs. OrigoDB vs. Sadas Engine vs. ToroDB

System Properties Comparison Oracle Berkeley DB vs. OrigoDB vs. Sadas Engine vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Widely used in-process key-value store

A fully ACID in-memory object graph database

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A MongoDB-compatible JSON document store, built on top of PostgreSQL

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

Relational DBMS

Document store

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	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

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

origodb.com

www.sadasengine.com

github.com/torodb/server

Technical documentation

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

origodb.com/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Robert Friberg et al

SADAS s.r.l.

8Kdata

Initial release

1994

2009

under the name LiveDB

2006

2016

Current release

18.1.40, May 2020

8.0

License

Commercial or Open Source

Open Source

commercial license available

Open Source

commercial

free trial version available

Open Source

AGPL-V3

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

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

C++

Java

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

AIX
Linux
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

string, integer, double, boolean, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

JDBC
ODBC
Proprietary protocol

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

managed by 'Learn by Usage'

User concepts

Access control

Role based authorization

Access rights for users, groups and roles according to SQL-standard

Access rights for users and roles

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

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

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

provided by Google News

Share this page