DBMS > Amazon DynamoDB vs. Coveo vs. Hyprcubd vs. Memcached vs. Sphinx

System Properties Comparison Amazon DynamoDB vs. Coveo vs. Hyprcubd vs. Memcached vs. Sphinx

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Serverless Time Series DBMS

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

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

Primary database model

Document store
Key-value store

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	2.34
Rank	#117	Overall
	#11	Search engines

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

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

aws.amazon.com/dynamodb

www.coveo.com

hyprcubd.com (offline)

www.memcached.org

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.coveo.com

github.com/memcached/memcached/wiki

sphinxsearch.com/docs

Developer

Amazon

Coveo

Hyprcubd, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Sphinx Technologies Inc.

Initial release

2012

2003

2001

Current release

1.6.25, March 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

BSD license

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
OS X
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API

gRPC (https)

Proprietary protocol

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Triggers

yes

by integration with AWS Lambda

yes

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

none

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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.

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

granular access controls, API key management, content filters

token access

yes

using SASL (Simple Authentication and Security Layer) protocol

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.