DBMS > Microsoft Azure Cosmos DB vs. searchxml vs. Tkrzw vs. VictoriaMetrics

System Properties Comparison Microsoft Azure Cosmos DB vs. searchxml vs. Tkrzw vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

DBMS for structured and unstructured content wrapped with an application server

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Native XML DBMS
Search engine

Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

azure.microsoft.com/services/cosmos-db

www.searchxml.net/category/products

dbmx.net/tkrzw

victoriametrics.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Microsoft

informationpartners gmbh

Mikio Hirabayashi

VictoriaMetrics

Initial release

2014

2015

2020

2018

Current release

1.0

0.9.3, August 2020

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2.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

C++

Server operating systems

hosted

Windows

Linux
macOS

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

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

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

RESTful HTTP API
WebDAV
XQuery
XSLT

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

C++

most other programming languages supported via APIs

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

yes

on the application server

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

sychronisation to multiple collections

none

Synchronous replication

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

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

yes

using specific database classes

User concepts

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.