DBMS > Amazon Redshift vs. Ingres vs. Manticore Search vs. Riak KV

System Properties Comparison Amazon Redshift vs. Ingres vs. Manticore Search vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Well established RDBMS

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

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Search engine

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	14.07
Rank	#38	Overall
	#23	Relational DBMS

Score	3.47
Rank	#79	Overall
	#43	Relational DBMS

Score	0.23
Rank	#300	Overall
	#21	Search engines

Score	3.67
Rank	#75	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.actian.com/databases/ingres

manticoresearch.com

Technical documentation

docs.aws.amazon.com/redshift

docs.actian.com/ingres

manual.manticoresearch.com

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

Developer

Amazon (based on PostgreSQL)

Actian Corporation

Manticore Software

OpenSource, formerly Basho Technologies

Initial release

2012

1974

originally developed at University Berkely in early 1970s

2017

2009

Current release

12.0, July 2024

6.0, February 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Linux
OS X

Data scheme

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.

but tools for importing/exporting data from/to XML-files available

Can index from XML

Secondary indexes

restricted

yes

full-text index on all search fields

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

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

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

user defined functions

in Python

yes

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

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

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

Synchronous replication based on Galera library

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 data sets can be stored

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

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

yes, using Riak Security

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.