DBMS > 4D vs. Amazon Redshift vs. Apache Kylin vs. Riak KV vs. XTDB

System Properties Comparison 4D vs. Amazon Redshift vs. Apache Kylin vs. Riak KV vs. XTDB

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 distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Distributed, fault tolerant key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document 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	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.4d.com

aws.amazon.com/redshift

kylin.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

kylin.apache.org/docs

www.tiot.jp/riak-docs/riak/kv/latest

www.xtdb.com/docs

Developer

4D, Inc

Amazon (based on PostgreSQL)

Apache Software Foundation, originally contributed from eBay Inc

OpenSource, formerly Basho Technologies

Juxt Ltd.

Initial release

1984

2012

2015

2009

2019

Current release

v20, April 2023

3.1.0, July 2020

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

MIT License

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

Erlang

Clojure

Server operating systems

OS X
Windows

hosted

Linux

Linux
OS X

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

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)

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

selectable replication factor

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes, using Riak Security

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.