DBMS > Amazon Redshift vs. CrateDB vs. Dgraph vs. IBM Cloudant

System Properties Comparison Amazon Redshift vs. CrateDB vs. Dgraph vs. IBM Cloudant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed Database based on Lucene

Distributed and scalable native Graph DBMS

Database as a Service offering based on Apache CouchDB

Primary database model

Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Graph DBMS

Document store

Secondary database models

Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

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

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

cratedb.com

dgraph.io

www.ibm.com/products/cloudant

Technical documentation

docs.aws.amazon.com/redshift

cratedb.com/docs

dgraph.io/docs

cloud.ibm.com/docs/Cloudant

Developer

Amazon (based on PostgreSQL)

Crate

Dgraph Labs, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2012

2013

2016

2010

Current release

5.8.1, August 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.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

Erlang

Server operating systems

hosted

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X
Windows

hosted

Data scheme

yes

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

schema-free

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, but no triggers and constraints, and PostgreSQL compatibility

APIs and other access methods

JDBC
ODBC

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.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

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions (Javascript)

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

Synchronous replication via Raft

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Read-after-write consistency on record level

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

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

ACID

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

rights management via user accounts

Planned for future releases

Access rights for users can be defined per database

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.