DBMS > Amazon DynamoDB vs. Infobright vs. TerminusDB vs. Tkrzw

System Properties Comparison Amazon DynamoDB vs. Infobright vs. TerminusDB vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Key-value store

Secondary database models

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	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/dynamodb

ignitetech.com/softwarelibrary/infobrightdb

terminusdb.com

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/dynamodb

terminusdb.github.io/terminusdb/#

Developer

Amazon

Ignite Technologies Inc.; formerly InfoBright Inc.

DataChemist Ltd.

Mikio Hirabayashi

Initial release

2012

2005

2018

2020

Current release

11.0.0, January 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPL V3

Open Source

Apache Version 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

Prolog, Rust

C++

Server operating systems

hosted

Linux
Windows

Linux

Linux
macOS

Data scheme

schema-free

yes

schema-free

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

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Journaling Streams

none

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

Durability

Support for making data persistent

yes

in-memory journaling

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

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

exploiting MySQL or PostgreSQL frontend capabilities

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.