DBMS > 4D vs. Amazon Redshift vs. Apache Druid vs. TerminusDB vs. Warp 10

System Properties Comparison 4D vs. Amazon Redshift vs. Apache Druid vs. TerminusDB vs. Warp 10

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Graph DBMS

Time Series DBMS

Secondary database models

Document store
RDF 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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.4d.com

aws.amazon.com/redshift

druid.apache.org

terminusdb.com

www.warp10.io

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

terminusdb.github.io/terminusdb/#

www.warp10.io/content/02_Getting_started

Developer

4D, Inc

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

DataChemist Ltd.

SenX

Initial release

1984

2012

2018

2015

Current release

v20, April 2023

29.0.1, April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

GPL V3

Open Source

Apache License 2.0

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

Prolog, Rust

Java

Server operating systems

OS X
Windows

hosted

Linux
OS X
Unix

Linux

Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

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

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

SQL for querying

SQL-like query language (WOQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP API
Jupyter
WebSocket

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Graph Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, via HDFS, S3 or other storage engines

Journaling Streams

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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 journaling

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Role-based access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.