DBMS > AgensGraph vs. Amazon Redshift vs. Manticore Search vs. RavenDB

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Manticore Search vs. RavenDB

Please select another system to include it in the comparison.

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

Multi-storage database for search, including full-text search.

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

Document store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Graph DBMS
Spatial DBMS
Time Series DBMS

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	0.22
Rank	#312	Overall
	#21	Search engines

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

manticoresearch.com

ravendb.net

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

manual.manticoresearch.com

ravendb.net/docs

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Manticore Software

Hibernating Rhinos

Initial release

2016

2012

2017

2010

Current release

2.1, December 2018

6.0, February 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL version 2

Open Source

AGPL version 3, commercial license available

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++

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
macOS
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

depending on used data model

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Synchronous replication based on Galera library

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

Authorization levels configured per client per database

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.