DBMS > Oracle Berkeley DB vs. Realm vs. Riak KV vs. Sadas Engine vs. Snowflake

System Properties Comparison Oracle Berkeley DB vs. Realm vs. Riak KV vs. Sadas Engine vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Distributed, fault tolerant key-value store

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational 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	7.60
Rank	#52	Overall
	#9	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

realm.io

www.sadasengine.com

www.snowflake.com

Technical documentation

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

realm.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

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

docs.snowflake.net/manuals/index.html

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Realm, acquired by MongoDB in May 2019

OpenSource, formerly Basho Technologies

SADAS s.r.l.

Snowflake Computing Inc.

Initial release

1994

2014

2009

2006

2014

Current release

18.1.40, May 2020

3.2.0, December 2022

8.0

License

Commercial or Open Source

Open Source

commercial license available

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version available

commercial

Cloud-based only

Only available as a cloud service

yes

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)

Erlang

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Android
Backend: server-less
iOS
Windows

Linux
OS X

AIX
Linux
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

CLI Client
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
Java

with Android only
Objective-C
React Native
Swift

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

Erlang

user defined functions

Triggers

yes

only for the SQL API

yes

Change Listeners

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

In-Memory realm

yes

managed by 'Learn by Usage'

User concepts

Access control

yes

yes, using Riak Security

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.