DBMS > 4D vs. Amazon Redshift vs. Cloudflare Workers KV vs. MaxDB vs. RavenDB

System Properties Comparison 4D vs. Amazon Redshift vs. Cloudflare Workers KV vs. MaxDB vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Large scale data warehouse service for use with business intelligence tools

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.32
Rank	#283	Overall
	#40	Key-value stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

www.4d.com

aws.amazon.com/redshift

www.cloudflare.com/developer-platform/workers-kv

maxdb.sap.com

ravendb.net

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

developers.cloudflare.com/kv/api

maxdb.sap.com/documentation

ravendb.net/docs

Developer

4D, Inc

Amazon (based on PostgreSQL)

Cloudflare

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

Hibernating Rhinos

Initial release

1984

2012

2018

1984

2010

Current release

v20, April 2023

7.9.10.12, February 2024

5.4, July 2022

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

AGPL version 3, commercial license available

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

C++

Server operating systems

OS X
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

yes

SQL-like query language (RQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

HTTP REST
Proprietary protocol

ADO.NET
JDBC
ODBC
WebDAV

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

.Net
C#
Java
Perl
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

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

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.