DBMS > Amazon Redshift vs. Ehcache vs. HEAVY.AI vs. Manticore Search vs. Tibero

System Properties Comparison Amazon Redshift vs. Ehcache vs. HEAVY.AI vs. Manticore Search vs. Tibero

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Secondary database models

Spatial DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

aws.amazon.com/redshift

www.ehcache.org

github.com/heavyai/heavydb
www.heavy.ai

manticoresearch.com

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

docs.heavy.ai

manual.manticoresearch.com

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

HEAVY.AI, Inc.

Manticore Software

TmaxSoft

Initial release

2012

2009

2016

2017

2003

Current release

3.10.0, March 2022

5.10, January 2022

6.0, February 2023

6, April 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2

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

Java

C++ and CUDA

C++

C and Assembler

Server operating systems

hosted

All OS with a Java VM

Linux

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

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

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.

Can index from XML

yes

Secondary indexes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

JCache

JDBC
ODBC
Thrift
Vega

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages supporting JDBC/ODBC

Java

All languages supporting JDBC/ODBC/Thrift
Python

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Persistent Stored Procedure (PSM)

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Round robin

Sharding

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

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

supports JTA and can work as an XA resource

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.