DBMS > AgensGraph vs. Amazon Redshift vs. Apache Drill vs. Graph Engine vs. Tkrzw

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Apache Drill vs. Graph Engine vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service for use with business intelligence tools

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Document store
Relational DBMS

Graph DBMS
Key-value store

Key-value store

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

drill.apache.org

www.graphengine.io

dbmx.net/tkrzw

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

www.graphengine.io/docs/manual

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Apache Software Foundation

Microsoft

Mikio Hirabayashi

Initial release

2016

2012

2010

2020

Current release

2.1, December 2018

1.20.3, January 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2

Open Source

MIT License

Open Source

Apache Version 2.0

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

.NET and C

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

.NET

Linux
macOS

Data scheme

depending on used data model

yes

schema-free

yes

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

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

C++

C#
C++
F#
Visual Basic

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

user defined functions

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

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.