DBMS > Amazon CloudSearch vs. Apache Impala vs. Coveo vs. Memcached vs. MySQL

System Properties Comparison Amazon CloudSearch vs. Apache Impala vs. Coveo vs. Memcached vs. MySQL

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Analytic DBMS for Hadoop

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

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.86
Rank	#133	Overall
	#12	Search engines

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/cloudsearch

Technical documentation

docs.aws.amazon.com/cloudsearch

impala.apache.org/impala-docs.html

docs.coveo.com

github.com/memcached/memcached/wiki

dev.mysql.com/doc

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Coveo

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2013

2012

2003

1995

Current release

4.1.0, June 2022

1.6.29, June 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

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

C and C++

Server operating systems

hosted

Linux

hosted

FreeBSD
Linux
OS X
Unix
Windows

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

yes

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

HTTP API

JDBC
ODBC

RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
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

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

yes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

selectable replication factor

yes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

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

User concepts

Access control

authentication via encrypted signatures

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

granular access controls, API key management, content filters

yes

using SASL (Simple Authentication and Security Layer) protocol

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.