DBMS > 4D vs. PlanetScale vs. Quasardb vs. SAP HANA vs. TerminusDB

System Properties Comparison 4D vs. PlanetScale vs. Quasardb vs. SAP HANA vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Distributed, high-performance timeseries database

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.4d.com

planetscale.com

quasar.ai

www.sap.com/products/hana.html

terminusdb.com

Technical documentation

terminusdb.github.io/terminusdb/#

Developer

4D, Inc

PlanetScale

quasardb

SAP

DataChemist Ltd.

Initial release

1984

2020

2009

2010

2018

Current release

v20, April 2023

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Prolog, Rust

Server operating systems

OS X
Windows

Docker
Linux
macOS

BSD
Linux
OS X
Windows

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

SQL-like query language

yes

SQL-like query language (WOQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

4D proprietary IDE
PHP

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Users and groups

Users with fine-grained authorization concept

no user groups or roles

Cryptographically strong user authentication and audit trail

yes

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.