DBMS > Datomic vs. EventStoreDB vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

System Properties Comparison Datomic vs. EventStoreDB vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

Editorial information provided by DB-Engines

Name

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

Description

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

www.datomic.com

www.eventstore.com

www.microsoft.com/en-us/sql-server

prometheus.io

github.com/torodb/server

Technical documentation

docs.datomic.com

developers.eventstore.com

learn.microsoft.com/en-US/sql/sql-server

prometheus.io/docs

Developer

Cognitect

Event Store Limited

Microsoft

8Kdata

Initial release

2012

1989

2015

2016

Current release

1.0.6735, June 2023

21.2, February 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL-V3

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java, Clojure

C++

Java

Server operating systems

All OS with a Java VM

Linux
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, integer, double, boolean, date, object_id

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP/JSON API

Supported programming languages

Clojure
Java

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes, but depending on the SQL-Server Edition

yes

by Federation

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

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

fine grained access rights according to SQL-standard

Access rights for users and 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.