DBMS > 4D vs. Heroic

System Properties Comparison 4D vs. Heroic

Please select another system to include it in the comparison.

Our visitors often compare 4D and Heroic with SAP Advantage Database Server.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Primary database model

Relational DBMS

Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.31
Rank	#112	Overall
	#54	Relational DBMS

Score	0.33
Rank	#280	Overall
	#24	Time Series DBMS

Website

www.4d.com

github.com/spotify/heroic

Technical documentation

developer.4d.com

spotify.github.io/heroic

Developer

4D, Inc

Spotify

Initial release

1984

2014

Current release

v20, April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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

Data scheme

yes

schema-free

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

via Elasticsearch

SQL

Support of SQL

yes

close to SQL 92

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

Supported programming languages

4D proprietary IDE
PHP

Server-side scripts

Stored procedures

yes

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

Foreign keys

Referential integrity

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.

User concepts

Access control

Users and groups

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Share this page