DBMS > Elasticsearch vs. PlanetScale vs. SAP HANA vs. Sphinx

System Properties Comparison Elasticsearch vs. PlanetScale vs. SAP HANA vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Search engine

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	1.75
Rank	#146	Overall
	#67	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

www.elastic.co/elasticsearch

planetscale.com

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

planetscale.com/docs

help.sap.com/hana

sphinxsearch.com/docs

Developer

Elastic

PlanetScale

SAP

Sphinx Technologies Inc.

Initial release

2010

2020

2010

2001

Current release

8.6, January 2023

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

yes

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

Java

C++

Server operating systems

All OS with a Java VM

Docker
Linux
macOS

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Proprietary protocol

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

SQLScript, R

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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.

Memcached and Redis integration

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

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.