DBMS > Amazon DynamoDB vs. SiteWhere vs. Teradata vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. SiteWhere vs. Teradata vs. TerminusDB

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

M2M integration platform for persisting/querying time series data

A hybrid cloud data analytics software platform (Teradata Vantage)

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

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF 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.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/dynamodb

github.com/sitewhere/sitewhere

www.teradata.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

sitewhere1.sitewhere.io/index.html

docs.teradata.com

terminusdb.github.io/terminusdb/#

Developer

Amazon

SiteWhere

Teradata

DataChemist Ltd.

Initial release

2012

2010

1984

2018

Current release

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Common Public Attribution License Version 1.0

commercial

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

Java

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Windows

hosted
Linux

Linux

Data scheme

schema-free

predefined scheme

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

HTTP REST

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Sharding

Hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

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

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

fine grained access rights according to SQL-standard

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.