DBMS > Amazon DynamoDB vs. Apache Druid vs. Manticore Search vs. MaxDB vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. Apache Druid vs. Manticore Search vs. MaxDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A robust and reliable RDBMS optimized to run all major SAP solutions

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

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Search engine

Relational DBMS

Graph DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

druid.apache.org/docs/latest/design

manual.manticoresearch.com

maxdb.sap.com/documentation

terminusdb.github.io/terminusdb/#

Developer

Amazon

Apache Software Foundation and contributors

Manticore Software

SAP, acquired from Software AG (Adabas-D) in 1997

DataChemist Ltd.

Initial release

2012

2017

1984

2018

Current release

29.0.1, April 2024

6.0, February 2023

7.9.10.12, February 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache license v2

Open Source

GPL version 2

commercial

Limited community edition free

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

C++

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Unix

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-less columns are supported

Fixed schema

yes

Typing

predefined data types such as float or date

yes

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

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

JDBC
RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
WebDAV

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
C#
Java
Perl
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

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

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Synchronous replication based on Galera library

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

in-memory journaling

In-memory capabilities

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

User concepts

Access control

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.