DBMS > KairosDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SiteWhere

System Properties Comparison KairosDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SiteWhere

Please select another system to include it in the comparison.

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

DBMS for structured and unstructured content wrapped with an application server

M2M integration platform for persisting/querying time series data

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Native XML DBMS
Search engine

Time Series DBMS

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	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

www.searchxml.net/category/products

github.com/sitewhere/sitewhere

Technical documentation

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

sitewhere1.sitewhere.io/index.html

Developer

Microsoft

informationpartners gmbh

SiteWhere

Initial release

2013

2014

2015

2010

Current release

1.2.2, November 2018

1.0

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.0

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

Java

Server operating systems

Linux
OS X
Windows

hosted

Windows

Linux
OS X
Windows

Data scheme

schema-free

predefined scheme

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

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
WebDAV
XQuery
XSLT

HTTP REST

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

JavaScript

yes

on the application server

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes

sychronisation to multiple collections

selectable replication factor

based on HBase

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

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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept

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.