DBMS > 4D vs. Datomic vs. Microsoft Azure Cosmos DB vs. STSdb vs. Yanza

System Properties Comparison 4D vs. Datomic vs. Microsoft Azure Cosmos DB vs. STSdb vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Globally distributed, horizontally scalable, multi-model database service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.4d.com

www.datomic.com

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

yanza.com

Technical documentation

developer.4d.com

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

Developer

4D, Inc

Cognitect

Microsoft

STS Soft SC

Yanza

Initial release

1984

2012

2014

2011

2015

Current release

v20, April 2023

1.0.6735, June 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPLv2, commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Server operating systems

OS X
Windows

All OS with a Java VM

hosted

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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 query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

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

.NET Client API

HTTP API

Supported programming languages

4D proprietary IDE
PHP

Clojure
Java

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

C#
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Transaction Functions

JavaScript

Triggers

yes

By using transaction functions

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

But extensive use of caching in the application peers

yes

Implicit feature of the cloud service

none

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

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.