DBMS > Amazon DynamoDB vs. HEAVY.AI vs. JanusGraph vs. Postgres-XL

System Properties Comparison Amazon DynamoDB vs. HEAVY.AI vs. JanusGraph vs. Postgres-XL

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A Graph DBMS optimized for distributed clusters

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	1.91
Rank	#135	Overall
	#12	Graph DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/dynamodb

github.com/heavyai/heavydb
www.heavy.ai

janusgraph.org

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.heavy.ai

docs.janusgraph.org

www.postgres-xl.org/documentation

Developer

Amazon

HEAVY.AI, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2012

2016

2017

2014

since 2012, originally named StormDB

Current release

5.10, January 2022

0.6.3, February 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

Mozilla public license

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 CUDA

Java

Server operating systems

hosted

Linux

Linux
OS X
Unix
Windows

Linux
macOS

Data scheme

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

All languages supporting JDBC/ODBC/Thrift
Python

Clojure
Java
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

yes

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

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

User authentification and security via Rexster Graph Server

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.