DBMS > 4D vs. Apache Druid vs. Interbase vs. Snowflake vs. TerminusDB

System Properties Comparison 4D vs. Apache Druid vs. Interbase vs. Snowflake vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Light-weight proven RDBMS

originally from Borland

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.4d.com

druid.apache.org

www.embarcadero.com/products/interbase

www.snowflake.com

terminusdb.com

Technical documentation

developer.4d.com

druid.apache.org/docs/latest/design

docs.embarcadero.com/products/interbase

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

4D, Inc

Apache Software Foundation and contributors

Embarcadero

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

1984

2012

1984

2014

2018

Current release

v20, April 2023

29.0.1, April 2024

InterBase 2020, December 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

GPL V3

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

Server operating systems

OS X
Windows

Linux
OS X
Unix

Android
iOS
Linux
OS X
Windows

hosted

Linux

Data scheme

yes

schema-less columns are supported

yes

support of semi-structured data formats (JSON, XML, Avro)

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

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

SQL for querying

yes

SQL-like query language (WOQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

4D proprietary IDE
PHP

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

none

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, via HDFS, S3 or other storage engines

Interbase Change Views

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.