DBMS > 4D vs. Amazon Redshift vs. Heroic vs. LeanXcale

System Properties Comparison 4D vs. Amazon Redshift vs. Heroic vs. LeanXcale

Please select another system to include it in the comparison.

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Primary database model

Relational DBMS

Time Series DBMS

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.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Website

www.4d.com

aws.amazon.com/redshift

github.com/spotify/heroic

www.leanxcale.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

spotify.github.io/heroic

Developer

4D, Inc

Amazon (based on PostgreSQL)

Spotify

LeanXcale

Initial release

1984

2012

2014

2015

Current release

v20, April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

via Elasticsearch

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

yes

through Apache Derby

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

C
Java
Scala

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

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

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.