DBMS > Amazon DynamoDB vs. CrateDB vs. RDF4J vs. TigerGraph

System Properties Comparison Amazon DynamoDB vs. CrateDB vs. RDF4J vs. TigerGraph

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

Distributed Database based on Lucene

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

RDF store

Graph DBMS

Secondary database models

Relational DBMS

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

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

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	1.44
Rank	#152	Overall
	#14	Graph DBMS

Website

aws.amazon.com/dynamodb

cratedb.com

rdf4j.org

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/dynamodb

cratedb.com/docs

rdf4j.org/documentation

docs.tigergraph.com

Developer

Amazon

Crate

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

Initial release

2012

2013

2004

2017

Current release

5.8.1, August 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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++

Server operating systems

hosted

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X
Unix
Windows

Linux

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

RDF Schemas

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.

Secondary indexes

yes

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Java
PHP
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions (Javascript)

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Read-after-write consistency on record level

Foreign keys

Referential integrity

yes

Relationships in graphs

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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.

User concepts

Access control

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

rights management via user accounts

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.