DBMS > Amazon DynamoDB vs. Firebird vs. GeoSpock vs. H2GIS vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. Firebird vs. GeoSpock vs. H2GIS vs. TerminusDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Firebird is an open source RDBMS forked from Borland's InterBase

Spatial and temporal data processing engine for extreme data scale

Spatial extension of H2

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Graph DBMS

Secondary database models

Time Series DBMS

Relational DBMS

Document store
RDF store

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	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/dynamodb

www.firebirdsql.org

geospock.com

www.h2gis.org

terminusdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

www.firebirdsql.org/en/reference-manuals

www.h2gis.org/docs/home

terminusdb.github.io/terminusdb/#

Developer

Amazon

Firebird Foundation

GeoSpock

CNRS

DataChemist Ltd.

Initial release

2012

2000

As fork of Borland's InterBase

2013

2018

Current release

5.0.0, January 2024

2.0, September 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Initial Developer's Public License

commercial

Open Source

LGPL 3.0

Open Source

GPL V3

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

Java, Javascript

Java

Prolog, Rust

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux

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

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java

JavaScript
Python

Server-side scripts

Stored procedures

PSQL

yes

based on H2

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

based on H2

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

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

Features a multi-generational MVCC architecture, readers do not block writers

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

in-memory journaling

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)

Users with fine-grained authorization concept

Access rights for users can be defined per table

yes

based on H2

Role-based access control

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.