DBMS > Altibase vs. Amazon Redshift vs. Elasticsearch vs. MySQL

System Properties Comparison Altibase vs. Amazon Redshift vs. Elasticsearch vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Large scale data warehouse service for use with business intelligence tools

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Widely used open source RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	0.87
Rank	#200	Overall
	#93	Relational DBMS

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	128.79
Rank	#8	Overall
	#1	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

altibase.com

aws.amazon.com/redshift

www.elastic.co/elasticsearch

www.mysql.com

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

docs.aws.amazon.com/redshift

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

dev.mysql.com/doc

Developer

Altibase

Amazon (based on PostgreSQL)

Elastic

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1999

2012

2010

1995

Current release

v7.3, 2023, August 2023

8.6, January 2023

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

Elastic License

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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++

Java

C and C++

Server operating systems

AIX
HP-UX
Linux

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

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.

yes

Secondary indexes

yes

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

ANSI SQL-92

yes

does not fully support an SQL-standard

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
ODBC

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java

All languages supporting JDBC/ODBC

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

stored procedures and stored functions

user defined functions

in Python

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.