DBMS > Memcached vs. SAP HANA vs. Sphinx

System Properties Comparison Memcached vs. SAP HANA vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Key-value store

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.memcached.org

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

github.com/memcached/memcached/wiki

help.sap.com/hana

sphinxsearch.com/docs

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Sphinx Technologies Inc.

Initial release

2003

2010

2001

Current release

1.6.25, March 2024

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Proprietary protocol

JDBC
ODBC

Proprietary protocol

Supported programming languages

.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

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

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.