DBMS > Amazon Redshift vs. Coveo vs. etcd vs. mSQL vs. Sphinx

System Properties Comparison Amazon Redshift vs. Coveo vs. etcd vs. mSQL vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

A distributed reliable key-value store

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

www.coveo.com

etcd.io
github.com/etcd-io/etcd

hughestech.com.au/products/msql

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

docs.coveo.com

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Coveo

Hughes Technologies

Sphinx Technologies Inc.

Initial release

2012

1994

2001

Current release

3.4, August 2019

4.4, October 2021

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

free licenses can be provided

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

C++

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

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

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

gRPC
JSON over HTTP

JDBC
ODBC

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C++
Delphi
Java
Perl
PHP
Tcl

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

Triggers

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

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.