DBMS > 4D vs. Amazon Redshift vs. Dragonfly vs. Microsoft Azure SQL Database vs. Tkrzw

System Properties Comparison 4D vs. Amazon Redshift vs. Dragonfly vs. Microsoft Azure SQL Database vs. Tkrzw

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 drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Database as a Service offering with high compatibility to Microsoft SQL Server

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.13
Rank	#114	Overall
	#54	Relational DBMS

Score	14.07
Rank	#38	Overall
	#23	Relational DBMS

Score	0.50
Rank	#245	Overall
	#35	Key-value stores

Score	76.53
Rank	#16	Overall
	#11	Relational DBMS

Score	0.00
Rank	#386	Overall
	#61	Key-value stores

Website

www.4d.com

aws.amazon.com/redshift

github.com/dragonflydb/dragonfly
www.dragonflydb.io

azure.microsoft.com/en-us/products/azure-sql/database

dbmx.net/tkrzw

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

www.dragonflydb.io/docs

docs.microsoft.com/en-us/azure/azure-sql

Developer

4D, Inc

Amazon (based on PostgreSQL)

DragonflyDB team and community contributors

Microsoft

Mikio Hirabayashi

Initial release

1984

2012

2023

2010

2020

Current release

v20, April 2023

1.0, March 2023

V12

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

commercial

Open Source

Apache Version 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

C++

Server operating systems

OS X
Windows

hosted

Linux

hosted

Linux
macOS

Data scheme

yes

scheme-free

yes

schema-free

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Lua

Transact SQL

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

yes, with always 3 replicas available

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

using specific database classes

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

Password-based authentication

fine grained access rights according to SQL-standard

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.