DBMS > 4D vs. BigObject vs. Microsoft Azure Cosmos DB vs. VoltDB vs. XTDB

System Properties Comparison 4D vs. BigObject vs. Microsoft Azure Cosmos DB vs. VoltDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Analytic DBMS for real-time computations and queries

Globally distributed, horizontally scalable, multi-model database service

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

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

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.4d.com

bigobject.io

azure.microsoft.com/services/cosmos-db

www.voltdb.com

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

Technical documentation

developer.4d.com

docs.bigobject.io

learn.microsoft.com/azure/cosmos-db

docs.voltdb.com

www.xtdb.com/docs

Developer

4D, Inc

BigObject, Inc.

Microsoft

VoltDB Inc.

Juxt Ltd.

Initial release

1984

2015

2014

2010

2019

Current release

v20, April 2023

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Open Source

MIT 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

Java, C++

Clojure

Server operating systems

OS X
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux
OS X

for development

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like DML and DDL statements

SQL-like query language

yes

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

fluentd
ODBC
RESTful HTTP API

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

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Lua

JavaScript

Java

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

User concepts

Access control

Users and groups

Access rights can be defined down to the item level

Users and roles with access to stored procedures

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.