DBMS > KairosDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Newts vs. Sphinx

System Properties Comparison KairosDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Newts vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Time Series DBMS based on Cassandra

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

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Time Series DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

opennms.github.io/newts

sphinxsearch.com

Technical documentation

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

sphinxsearch.com/docs

Developer

Microsoft

OpenNMS Group

Sphinx Technologies Inc.

Initial release

2013

2014

2012

2014

2001

Current release

1.2.2, November 2018

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

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++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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 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

Graphite protocol
HTTP REST
Telnet API

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

RESTful HTTP API

HTTP REST
Java API

Proprietary protocol

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

optimistic locking

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

simple password-based access control

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.