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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

Document store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Website

github.com/Softmotions/ejdb

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

www.searchxml.net/category/products

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

Developer

Softmotions

Microsoft

informationpartners gmbh

Initial release

2012

2013

2014

2015

Current release

1.2.2, November 2018

1.0

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

commercial

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

server-less

Linux
OS X
Windows

hosted

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

in-process shared library

Graphite protocol
HTTP REST
Telnet API

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

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

none

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes

sychronisation to multiple collections

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

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.