DBMS > 4D vs. Graph Engine vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Newts

System Properties Comparison 4D vs. Graph Engine vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Newts

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A robust and reliable RDBMS optimized to run all major SAP solutions

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS based on Cassandra

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

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

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Website

www.4d.com

www.graphengine.io

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

opennms.github.io/newts

Technical documentation

developer.4d.com

www.graphengine.io/docs/manual

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

Developer

4D, Inc

Microsoft

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

OpenNMS Group

Initial release

1984

2010

1984

2014

Current release

v20, April 2023

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Limited community edition free

commercial

Open Source

Apache 2.0

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

.NET and C

C++

Java

Server operating systems

OS X
Windows

.NET

AIX
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

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

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

RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

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

HTTP REST
Java API

Supported programming languages

4D proprietary IDE
PHP

C#
C++
F#
Visual Basic

.Net
C#
Java
Perl
PHP
Python

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

Java

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Implicit feature of the cloud service

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

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.