DBMS > Interbase vs. Kinetica vs. PlanetScale vs. SAP HANA vs. TerarkDB

System Properties Comparison Interbase vs. Kinetica vs. PlanetScale vs. SAP HANA vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

Fully vectorized database across both GPUs and CPUs

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

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

www.embarcadero.com/products/interbase

www.kinetica.com

planetscale.com

www.sap.com/products/hana.html

github.com/bytedance/terarkdb

Technical documentation

docs.embarcadero.com/products/interbase

docs.kinetica.com

planetscale.com/docs

help.sap.com/hana

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Embarcadero

Kinetica

PlanetScale

SAP

ByteDance, originally Terark

Initial release

1984

2012

2020

2010

2016

Current release

InterBase 2020, December 2019

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

restricted open source version available

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, C++

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux

Docker
Linux
macOS

Appliance or cloud-service

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

C++ API
Java API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

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

C++
Java

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

yes

proprietary syntax

SQLScript, R

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Source-replica replication

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Users with fine-grained authorization concept

no user groups or roles

yes

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.