DBMS > Datomic vs. IBM Cloudant vs. Microsoft SQL Server vs. Tkrzw

System Properties Comparison Datomic vs. IBM Cloudant vs. Microsoft SQL Server vs. Tkrzw

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

Database as a Service offering based on Apache CouchDB

Microsofts flagship relational DBMS

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

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.66
Rank	#144	Overall
	#66	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

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

Website

www.datomic.com

www.ibm.com/products/cloudant

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

dbmx.net/tkrzw

Technical documentation

docs.datomic.com

cloud.ibm.com/docs/Cloudant

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

Developer

Cognitect

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Mikio Hirabayashi

Initial release

2012

2010

1989

2020

Current release

1.0.7075, December 2023

SQL Server 2022, November 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial

limited edition free

commercial

restricted free version is available

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.

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

Erlang

C++

Server operating systems

All OS with a Java VM

hosted

Linux
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

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

Supported programming languages

Clojure
Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

View functions (Map-Reduce) in JavaScript

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

Sharding

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

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, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

using specific database classes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.