DBMS > AgensGraph vs. Amazon Redshift vs. Coveo vs. LeanXcale vs. Riak TS

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Coveo vs. LeanXcale vs. Riak TS

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

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

Key-value store
Relational DBMS

Time Series DBMS

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.11
Rank	#118	Overall
	#11	Search engines

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

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

www.coveo.com

www.leanxcale.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

docs.coveo.com

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Coveo

LeanXcale

Open Source, formerly Basho Technologies

Initial release

2016

2012

2015

Current release

2.1, December 2018

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

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

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X

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

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

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

through Apache Derby

yes, limited

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

RESTful HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

HTTP API
Native Erlang Interface

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

C
Java
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between datasets can be stored

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.