DBMS > Amazon Redshift vs. AnzoGraph DB vs. CouchDB vs. TigerGraph

System Properties Comparison Amazon Redshift vs. AnzoGraph DB vs. CouchDB vs. TigerGraph

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

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

cambridgesemantics.com/anzograph

couchdb.apache.org

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.couchdb.org/en/stable

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Cambridge Semantics

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Initial release

2012

2018

2005

2017

Current release

2.3, January 2021

3.3.3, December 2023

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache version 2

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

Erlang

C++

Server operating systems

hosted

Linux

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Schema-free and OWL/RDFS-schema support

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.

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL and SPARQL* as primary query language. Cypher preview.

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

RESTful HTTP/JSON API

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

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
Python

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

improved architecture with release 2.0

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in MPP-Cluster

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in MPP-Cluster

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

not needed in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

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

Access rights for users and roles

Access rights for users can be defined per database

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.