DBMS > Amazon DynamoDB vs. BigObject vs. EsgynDB vs. GeoMesa vs. Realm

System Properties Comparison Amazon DynamoDB vs. BigObject vs. EsgynDB vs. GeoMesa vs. Realm

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Spatial DBMS

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.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

docs.bigobject.io

www.geomesa.org/documentation/stable/user/index.html

realm.io/docs

Developer

Amazon

BigObject, Inc.

Esgyn

CCRi and others

Realm, acquired by MongoDB in May 2019

Initial release

2012

2015

2014

Current release

4.0.5, February 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free community edition available

commercial

Open Source

Apache License 2.0

Open Source

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

Scala

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)

Linux

Android
Backend: server-less
iOS
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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

runs within the applications so server-side scripts are unnecessary

Triggers

yes

by integration with AWS Lambda

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication between multi datacenters

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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

depending on storage layer

yes

In-Memory realm

User concepts

Access control

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

yes

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.