DBMS > InfinityDB vs. Microsoft Azure Cosmos DB vs. MySQL vs. XTDB

System Properties Comparison InfinityDB vs. Microsoft Azure Cosmos DB vs. MySQL vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A Java embedded Key-Value Store which extends the Java Map interface

Globally distributed, horizontally scalable, multi-model database service

Widely used open source RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#59	Key-value stores

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

boilerbay.com

azure.microsoft.com/services/cosmos-db

www.mysql.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

boilerbay.com/infinitydb/manual

learn.microsoft.com/azure/cosmos-db

dev.mysql.com/doc

www.xtdb.com/docs

Developer

Boiler Bay Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Juxt Ltd.

Initial release

2002

2014

1995

2019

Current release

4.0

9.0.0, July 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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

Clojure

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

JSON types

yes

yes, extensible-data-notation format

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

manual creation possible, using inversions based on multi-value capability

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

Java

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

JavaScript

yes

proprietary syntax

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

yes, each node contains all data

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

Multi-item ACID transactions with snapshot isolation within a partition

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights can be defined down to the item level

Users with fine-grained authorization concept

no user groups or roles

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.