DBMS > Apache Impala vs. Microsoft Azure Cosmos DB vs. Sphinx vs. Yanza

System Properties Comparison Apache Impala vs. Microsoft Azure Cosmos DB vs. Sphinx vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Analytic DBMS for Hadoop

Globally distributed, horizontally scalable, multi-model database service

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Time Series DBMS

Secondary database models

Document store

Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

impala.apache.org

azure.microsoft.com/services/cosmos-db

sphinxsearch.com

yanza.com

Technical documentation

impala.apache.org/impala-docs.html

learn.microsoft.com/azure/cosmos-db

sphinxsearch.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Microsoft

Sphinx Technologies Inc.

Yanza

Initial release

2013

2014

2001

2015

Current release

4.1.0, June 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2, commercial licence available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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 properties auto-indexed by default

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

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

Proprietary protocol

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

JavaScript

Triggers

JavaScript

yes

Timer and event based

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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.

yes

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, groups and roles

based on Apache Sentry and Kerberos

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.