DBMS > 4D vs. BigObject vs. Ehcache vs. Microsoft Azure Cosmos DB vs. RocksDB

System Properties Comparison 4D vs. BigObject vs. Ehcache vs. Microsoft Azure Cosmos DB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

Globally distributed, horizontally scalable, multi-model database service

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.4d.com

bigobject.io

www.ehcache.org

azure.microsoft.com/services/cosmos-db

rocksdb.org

Technical documentation

developer.4d.com

docs.bigobject.io

www.ehcache.org/documentation

learn.microsoft.com/azure/cosmos-db

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

BigObject, Inc.

Terracotta Inc, owned by Software AG

Microsoft

Facebook, Inc.

Initial release

1984

2015

2009

2014

2013

Current release

v20, April 2023

3.10.0, March 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

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++

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)

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

fluentd
ODBC
RESTful HTTP API

JCache

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

C++ API
Java API

Supported programming languages

4D proprietary IDE
PHP

Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Lua

JavaScript

Triggers

yes

Cache Event Listeners

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

by using Terracotta Server

yes

Implicit feature of the cloud service

yes

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

Tunable Consistency (Strong, Eventual, Weak)

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

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

Multi-item ACID transactions with snapshot isolation within a partition

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

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.