DBMS > Elasticsearch vs. Galaxybase vs. Microsoft Azure Cosmos DB vs. Sphinx

System Properties Comparison Elasticsearch vs. Galaxybase vs. Microsoft Azure Cosmos DB 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, ACID-compliant native distributed parallel graph platform

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Search engine

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.elastic.co/elasticsearch

galaxybase.com

azure.microsoft.com/services/cosmos-db

sphinxsearch.com

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

sphinxsearch.com/docs

Developer

Elastic

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Microsoft

Sphinx Technologies Inc.

Initial release

2010

2017

2014

2001

Current release

8.6, January 2023

Nov 20, November 2021

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

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C and Java

C++

Server operating systems

All OS with a Java VM

Linux

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

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

Strong typed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

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

Java API
RESTful HTTP/JSON API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Proprietary protocol

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Go
Java
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

user defined procedures and functions

JavaScript

Triggers

yes

by using the 'percolation' feature

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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.

Memcached and Redis integration

yes

User concepts

Access control

Role-based access control

Access rights can be defined down to the item level

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.