DBMS > Amazon DynamoDB vs. Geode vs. Google Cloud Firestore vs. OrigoDB vs. SpatiaLite

System Properties Comparison Amazon DynamoDB vs. Geode vs. Google Cloud Firestore vs. OrigoDB vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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 fully ACID in-memory object graph database

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Key-value store

Document store

Document store
Object oriented DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

aws.amazon.com/dynamodb

geode.apache.org

firebase.google.com/products/firestore

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

docs.aws.amazon.com/dynamodb

geode.apache.org/docs

firebase.google.com/docs/firestore

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Amazon

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Robert Friberg et al

Alessandro Furieri

Initial release

2012

2002

2017

2009

under the name LiveDB

2008

Current release

1.1, February 2017

5.0.0, August 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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++

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
Windows

server-less

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

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

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

.Net

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes, with Cloud Functions

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

yes, on a single node

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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 per client and object definable

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Role based authorization

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.