DBMS > Amazon DynamoDB vs. Heroic vs. Ignite vs. Oracle Berkeley DB vs. Percona Server for MongoDB

System Properties Comparison Amazon DynamoDB vs. Heroic vs. Ignite vs. Oracle Berkeley DB vs. Percona Server for MongoDB

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Widely used in-process key-value store

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

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

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

aws.amazon.com/dynamodb

github.com/spotify/heroic

ignite.apache.org

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

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.aws.amazon.com/dynamodb

spotify.github.io/heroic

apacheignite.readme.io/docs

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

docs.percona.com/percona-distribution-for-mongodb

Developer

Amazon

Spotify

Apache Software Foundation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Percona

Initial release

2012

2014

2015

1994

2015

Current release

Apache Ignite 2.6

18.1.40, May 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

GPL Version 2

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

Java

C++, Java, .Net

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

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

yes

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

yes

via Elasticsearch

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol using JSON

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
Java
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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes

by integration with AWS Lambda

yes (cache interceptors and events)

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

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

via In-Memory Engine

User concepts

Access control

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

Security Hooks for custom implementations

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.