DBMS > 4D vs. BigObject vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. PlanetScale

System Properties Comparison 4D vs. BigObject vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. PlanetScale

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

Analytic DBMS for real-time computations and queries

A multi-model DBMS and application server

Globally distributed, horizontally scalable, multi-model database service

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store
Object oriented DBMS
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

Document store
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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

www.4d.com

bigobject.io

www.intersystems.com/products/cache

azure.microsoft.com/services/cosmos-db

planetscale.com

Technical documentation

developer.4d.com

docs.bigobject.io

docs.intersystems.com

learn.microsoft.com/azure/cosmos-db

planetscale.com/docs

Developer

4D, Inc

BigObject, Inc.

InterSystems

Microsoft

PlanetScale

Initial release

1984

2015

1997

2014

2020

Current release

v20, April 2023

2018.1.4, May 2020

License

Commercial or Open Source

commercial

free community edition available

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

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)

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

hosted

Docker
Linux
macOS

Data scheme

yes

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like DML and DDL statements

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

fluentd
ODBC
RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

4D proprietary IDE
PHP

C#
C++
Java

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

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

Server-side scripts

Stored procedures

yes

Lua

yes

JavaScript

yes

proprietary syntax

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles

Access rights can be defined down to the item level

Users with fine-grained authorization concept

no user groups or roles

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.