DBMS > Dolt vs. FatDB vs. IBM Cloudant vs. Transbase

System Properties Comparison Dolt vs. FatDB vs. IBM Cloudant vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Database as a Service offering based on Apache CouchDB

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

www.ibm.com/products/cloudant

www.transaction.de/en/products/transbase.html

Technical documentation

docs.dolthub.com

cloud.ibm.com/docs/Cloudant

www.transaction.de/en/products/transbase/features.html

Developer

DoltHub Inc

FatCloud

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Transaction Software GmbH

Initial release

2018

2012

2010

1987

Current release

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free development 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

Erlang

C and C++

Server operating systems

Linux
macOS
Windows

Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

CLI Client
HTTP REST

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

via applications

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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.

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
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

yes

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

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

Can implement custom security layer via applications

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.

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

Are you still not using Version Control for Data?
11 April 2020, Towards Data Science

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Share this page