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

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

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

Relational DBMS

Document store
Key-value store

Document 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.27
Rank	#297	Overall
	#44	Document stores

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Website

www.4d.com

aws.amazon.com/redshift

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

github.com/Softmotions/ejdb

kyligence.io/kyligence-enterprise

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

github.com/Softmotions/ejdb/blob/master/README.md

Developer

4D, Inc

Amazon (based on PostgreSQL)

Atos Convergence Creators

Softmotions

Kyligence, Inc.

Initial release

1984

2012

2016

2012

2016

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

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

Server operating systems

OS X
Windows

hosted

Linux

server-less

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

yes

string, integer, double, bool, date, object_id

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)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

LDAP

in-process shared library

JDBC
ODBC
RESTful HTTP API

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
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

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

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.