DBMS > Amazon DynamoDB vs. Graph Engine vs. Manticore Search vs. RDF4J vs. TimescaleDB

System Properties Comparison Amazon DynamoDB vs. Graph Engine vs. Manticore Search vs. RDF4J vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Multi-storage database for search, including full-text search.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store
Key-value store

Graph DBMS
Key-value store

Search engine

RDF store

Time Series DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS

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	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

www.graphengine.io/docs/manual

manual.manticoresearch.com

rdf4j.org/documentation

docs.timescale.com

Developer

Amazon

Microsoft

Manticore Software

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Timescale

Initial release

2012

2010

2017

2004

2017

Current release

6.0, February 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache 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

.NET and C

C++

Java

Server operating systems

hosted

.NET

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Fixed schema

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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 index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

none

Source-replica replication with hot standby and reads on replicas

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

The original contents of fields are not stored in the Manticore index.

yes

in-memory storage is supported as well

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)

fine grained access rights according to SQL-standard

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.