DBMS > Amazon Redshift vs. Citus vs. Ehcache vs. Sphinx vs. SwayDB

System Properties Comparison Amazon Redshift vs. Citus vs. Ehcache vs. Sphinx vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

A widely adopted Java cache with tiered storage options

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

www.ehcache.org/documentation

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Sphinx Technologies Inc.

Simer Plaha

Initial release

2012

2010

2009

2001

2018

Current release

8.1, December 2018

3.10.0, March 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2, commercial licence available

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

hosted

Linux

All OS with a Java VM

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

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

specific XML type available, but no XML query functionality

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JCache

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Java

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

yes

by using Terracotta Server

none

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

Atomic execution of operations

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

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.