DBMS > 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. Kyligence Enterprise vs. VoltDB

System Properties Comparison 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. Kyligence Enterprise vs. VoltDB

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

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

A distributed analytics engine for big data, built on top of Apache Kylin

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store
Key-value store

Relational 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.40
Rank	#269	Overall
	#124	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.4d.com

aws.amazon.com/redshift

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

kyligence.io/kyligence-enterprise

www.voltdb.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

docs.voltdb.com

Developer

4D, Inc

Amazon (based on PostgreSQL)

Atos Convergence Creators

Kyligence, Inc.

VoltDB Inc.

Initial release

1984

2012

2016

2010

Current release

v20, April 2023

1703

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

OS X
Windows

hosted

Linux

Linux
OS X

for development

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

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

ANSI SQL for queries (using Apache Calcite)

yes

only a subset of SQL 99

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

LDAP

JDBC
ODBC
RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

LDAP bind authentication

Users and roles with access to stored procedures

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.