DBMS > AgensGraph vs. Amazon Redshift vs. Google Cloud Spanner vs. Manticore Search

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Google Cloud Spanner vs. Manticore Search

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

cloud.google.com/spanner

manticoresearch.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

manual.manticoresearch.com

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Google

Manticore Software

Initial release

2016

2012

2017

Current release

2.1, December 2018

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL version 2

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

Data scheme

depending on used data model

yes

Fixed schema

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

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

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

in Python

user defined functions

Triggers

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication with 3 replicas for regional instances.

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

yes

isolated transactions for atomic changes and binary logging for safe writes

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.

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.