DBMS > BoltDB vs. Cassandra vs. Oracle Berkeley DB vs. Riak TS

System Properties Comparison BoltDB vs. Cassandra vs. Oracle Berkeley DB vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Widely used in-process key-value store

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Key-value store

Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Secondary database models

Vector DBMS

starting with release V5

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

github.com/boltdb/bolt

cassandra.apache.org

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

Technical documentation

cassandra.apache.org/doc/latest

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

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

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Open Source, formerly Basho Technologies

Initial release

2013

2008

1994

2015

Current release

4.1.3, July 2023

18.1.40, May 2020

3.0.0, September 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

commercial license available

Open Source

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

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

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Data scheme

schema-free

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

restricted

only equality queries, not always the best performing solution

yes

restricted

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

SQL interfaced based on SQLite is available

yes, limited

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

.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

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

Server-side scripts

Stored procedures

Erlang

Triggers

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Representation of geographical distribution of servers is possible

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

Atomicity and isolation are supported for single operations

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

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.