DBMS > Amazon DynamoDB vs. Badger vs. Google Cloud Datastore vs. H2 vs. STSdb

System Properties Comparison Amazon DynamoDB vs. Badger vs. Google Cloud Datastore vs. H2 vs. STSdb

Editorial information provided by DB-Engines

Name

Description

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

Secondary database models

Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

aws.amazon.com/dynamodb

github.com/dgraph-io/badger

cloud.google.com/datastore

www.h2database.com

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/dynamodb

godoc.org/github.com/dgraph-io/badger

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

Developer

Amazon

DGraph Labs

Google

Thomas Mueller

STS Soft SC

Initial release

2012

2017

2008

2005

2011

Current release

2.2.220, July 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

GPLv2, 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

Java

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

primitive types and user defined types (classes)

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

.NET Client API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures and User-Defined Functions

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights 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.