DBMS > Amazon DynamoDB vs. BigObject vs. Ehcache vs. Google Cloud Firestore vs. JanusGraph

System Properties Comparison Amazon DynamoDB vs. BigObject vs. Ehcache vs. Google Cloud Firestore vs. JanusGraph

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Document store

Graph DBMS

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

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Website

aws.amazon.com/dynamodb

bigobject.io

www.ehcache.org

firebase.google.com/products/firestore

janusgraph.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.bigobject.io

www.ehcache.org/documentation

firebase.google.com/docs/firestore

docs.janusgraph.org

Developer

Amazon

BigObject, Inc.

Terracotta Inc, owned by Software AG

Google

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2012

2015

2009

2017

Current release

3.10.0, March 2022

0.6.3, February 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

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

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP API

fluentd
ODBC
RESTful HTTP API

JCache

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

by using Terracotta Server

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

by using Terracotta Server

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Using Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Relationships in graphs

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

yes

supports JTA and can work as an XA resource

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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. Security Rules for 3rd party authentication using Firebase Auth.

User authentification and security via Rexster Graph Server

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.