DBMS > Amazon CloudSearch vs. Amazon DynamoDB vs. IBM Db2 vs. JanusGraph vs. Tarantool

System Properties Comparison Amazon CloudSearch vs. Amazon DynamoDB vs. IBM Db2 vs. JanusGraph vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Search engine

Document store
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Graph DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

with Tarantool/GIS extension

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

aws.amazon.com/cloudsearch

aws.amazon.com/dynamodb

www.ibm.com/products/db2

janusgraph.org

www.tarantool.io

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.aws.amazon.com/dynamodb

www.ibm.com/docs/en/db2

docs.janusgraph.org

www.tarantool.io/en/doc

Developer

Amazon

IBM

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2012

1983

host version

2017

2008

Current release

12.1, October 2016

0.6.3, February 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free version is available

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Unix
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

HTTP API

RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Open binary protocol

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Clojure
Java
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

only with Windows/Unix/Linux Version

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

with separate tools (MQ, InfoSphere)

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes, write ahead logging

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

authentication via encrypted signatures

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

User authentification and security via Rexster Graph Server

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.