DBMS > Amazon DynamoDB vs. Couchbase vs. Oracle Berkeley DB vs. Splice Machine

System Properties Comparison Amazon DynamoDB vs. Couchbase vs. Oracle Berkeley DB vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Widely used in-process key-value store

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store
Key-value store

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	16.74
Rank	#33	Overall
	#5	Document stores

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

Score	0.54
Rank	#244	Overall
	#114	Relational DBMS

Website

aws.amazon.com/dynamodb

www.couchbase.com

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

splicemachine.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchbase.com

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

splicemachine.com/how-it-works

Developer

Amazon

Couchbase, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Splice Machine

Initial release

2012

2011

1994

2014

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

18.1.40, May 2020

3.1, March 2021

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

commercial license available

Open Source

AGPL 3.0, commercial license available

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, C++, Go and Erlang

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

Java

Server operating systems

hosted

Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

RESTful HTTP API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

Java

Triggers

yes

by integration with AWS Lambda

yes

via the TAP protocol

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Ephemeral buckets

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Access rights for users, groups and roles 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.