DBMS > 4D vs. Amazon Redshift vs. Apache Druid vs. Atos Standard Common Repository vs. Tkrzw

System Properties Comparison 4D vs. Amazon Redshift vs. Apache Druid vs. Atos Standard Common Repository vs. Tkrzw

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Large scale data warehouse service for use with business intelligence tools

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Key-value 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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.4d.com

aws.amazon.com/redshift

druid.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

dbmx.net/tkrzw

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

Developer

4D, Inc

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Atos Convergence Creators

Mikio Hirabayashi

Initial release

1984

2012

2016

2020

Current release

v20, April 2023

29.0.1, April 2024

1703

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache license v2

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

Java

C++

Server operating systems

OS X
Windows

hosted

Linux
OS X
Unix

Linux

Linux
macOS

Data scheme

yes

schema-less columns are supported

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL for querying

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

LDAP

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages with LDAP bindings

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, via HDFS, S3 or other storage engines

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

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

using specific database classes

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

LDAP bind authentication

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.