DBMS > 4D vs. Dolt vs. HBase vs. Microsoft Azure Cosmos DB

System Properties Comparison 4D vs. Dolt vs. HBase vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.4d.com

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

hbase.apache.org

azure.microsoft.com/services/cosmos-db

Technical documentation

developer.4d.com

docs.dolthub.com

hbase.apache.org/book.html

learn.microsoft.com/azure/cosmos-db

Developer

4D, Inc

DoltHub Inc

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Initial release

1984

2018

2008

2014

Current release

v20, April 2023

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache version 2

commercial

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

Java

Server operating systems

OS X
Windows

Linux
macOS
Windows

Linux
Unix
Windows

using Cygwin

hosted

Data scheme

yes

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

close to SQL 92

yes

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

CLI Client
HTTP REST

Java API
RESTful HTTP API
Thrift

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

4D proprietary IDE
PHP

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Coprocessors in Java

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

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.

yes

User concepts

Access control

Users and groups

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights can be defined down to the item level

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.