DBMS > 4D vs. Amazon Redshift vs. HarperDB vs. KeyDB vs. STSdb

System Properties Comparison 4D vs. Amazon Redshift vs. HarperDB vs. KeyDB vs. STSdb

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Document store

Key-value store

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.55
Rank	#248	Overall
	#38	Document stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

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

Website

www.4d.com

aws.amazon.com/redshift

www.harperdb.io

github.com/Snapchat/KeyDB
keydb.dev

github.com/STSSoft/STSdb4

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

docs.harperdb.io/docs

docs.keydb.dev

Developer

4D, Inc

Amazon (based on PostgreSQL)

HarperDB

EQ Alpha Technology Ltd.

STS Soft SC

Initial release

1984

2012

2017

2019

2011

Current release

v20, April 2023

3.1, August 2021

4.0.8, September 2015

License

Commercial or Open Source

commercial

free community edition available

Open Source

BSD-3

Open Source

GPLv2, 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

Node.js

C++

Server operating systems

OS X
Windows

hosted

Linux
OS X

Linux

Windows

Data scheme

yes

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON data types

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

restricted

yes

by using the Redis Search module

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

SQL-like data manipulation statements

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Proprietary protocol

RESP - REdis Serialization Protoco

.NET Client API

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Custom Functions

since release 3.1

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

A table resides as a whole on one (or more) nodes in a cluster

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

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
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic execution of specific operations

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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 for users and roles

simple password-based access control and ACL

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.