DBMS > Amazon Redshift vs. AnzoGraph DB vs. Brytlyt vs. Datomic

System Properties Comparison Amazon Redshift vs. AnzoGraph DB vs. Brytlyt vs. Datomic

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Primary database model

Relational DBMS

Graph DBMS
RDF store

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.22
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Website

aws.amazon.com/redshift

cambridgesemantics.com/anzograph

brytlyt.io

www.datomic.com

Technical documentation

docs.aws.amazon.com/redshift

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

docs.brytlyt.io

docs.datomic.com

Developer

Amazon (based on PostgreSQL)

Cambridge Semantics

Brytlyt

Cognitect

Initial release

2012

2018

2016

2012

Current release

2.3, January 2021

5.0, August 2023

1.0.7180, July 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

limited edition free

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, C++ and CUDA

Java, Clojure

Server operating systems

hosted

Linux

Linux
OS X
Windows

All OS with a Java VM

Data scheme

yes

Schema-free and OWL/RDFS-schema support

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

specific XML-type available, but no XML query functionality.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

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

yes

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
Python

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

user defined functions

in PL/pgSQL

yes

Transaction Functions

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

But extensive use of caching in the application peers

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in MPP-Cluster

Source-replica replication

none

But extensive use of caching in the application peers

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

not needed in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.