DBMS > AgensGraph vs. Amazon Redshift vs. Citus vs. Coveo vs. LeanXcale

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Citus vs. Coveo vs. LeanXcale

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

Key-value store
Relational DBMS

Secondary database models

Document store

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

www.citusdata.com

www.coveo.com

www.leanxcale.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

docs.coveo.com

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Coveo

LeanXcale

Initial release

2016

2012

2010

2012

2015

Current release

2.1, December 2018

8.1, December 2018

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL, commercial license also available

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

Server operating systems

Linux
OS X
Windows

hosted

Linux

hosted

Data scheme

depending on used data model

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

yes

through Apache Derby

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

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

RESTful HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript
Python

C
Java
Scala

Server-side scripts

Stored procedures

yes

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

other methods possible by using 3rd party extensions

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

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

granular access controls, API key management, content filters

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.