DBMS > Datomic vs. VelocityDB vs. Vitess vs. XTDB

System Properties Comparison Datomic vs. VelocityDB vs. Vitess vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Relational DBMS

Graph DBMS
Object oriented DBMS

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.datomic.com

velocitydb.com

vitess.io

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

Technical documentation

docs.datomic.com

velocitydb.com/UserGuide

vitess.io/docs

www.xtdb.com/docs

Developer

Cognitect

VelocityDB Inc

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2012

2011

2013

2019

Current release

1.0.6735, June 2023

7.x

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Clojure

Server operating systems

All OS with a Java VM

Any that supports .NET

Docker
Linux
macOS

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

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

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP API

.Net

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

Clojure
Java

.Net

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

yes

Transaction Functions

yes

proprietary syntax

Triggers

By using transaction functions

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

Based on Windows Authentication

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.

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

Atomic Canyon and ORNL develop revolutionary nuclear AI
16 May 2024, energynews.pro

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Brazil’s Nubank acquires US software firm Cognitect, creator of Clojure and Datomic
24 July 2020, LatamList

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page