DBMS > Amazon Redshift vs. Elasticsearch vs. HEAVY.AI vs. Sphinx

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. HEAVY.AI vs. Sphinx

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

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

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

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

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

docs.heavy.ai

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Elastic

HEAVY.AI, Inc.

Sphinx Technologies Inc.

Initial release

2012

2010

2016

2001

Current release

8.6, January 2023

5.10, January 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2, commercial licence 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

Java

C++ and CUDA

C++

Server operating systems

hosted

All OS with a Java VM

Linux

FreeBSD
Linux
NetBSD
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.

Secondary indexes

restricted

yes

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/Thrift
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

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

Transaction concepts

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

ACID

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 Sphinx index.

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

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.