DBMS > Dolt vs. IRONdb vs. Microsoft Azure Table Storage vs. XTDB

System Properties Comparison Dolt vs. IRONdb vs. Microsoft Azure Table Storage vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

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

Primary database model

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/dolthub/dolt
www.dolthub.com

www.circonus.com/solutions/time-series-database/

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

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

Technical documentation

docs.dolthub.com

docs.circonus.com/irondb/category/getting-started

www.xtdb.com/docs

Developer

DoltHub Inc

Circonus LLC.

Microsoft

Juxt Ltd.

Initial release

2018

2017

2012

2019

Current release

V0.10.20, January 2018

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

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

C and C++

Clojure

Server operating systems

Linux
macOS
Windows

Linux

hosted

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

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

CLI Client
HTTP REST

HTTP API

RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Clojure
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

configurable replication factor, datacenter aware

yes

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

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

25 Hot New Data Tools and What They DON'T Do
14 May 2020, Towards Data Science

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

Inside Azure File Storage
7 October 2015, azure.microsoft.com

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Share this page