DBMS > Interbase vs. Kinetica vs. Manticore Search vs. SAP HANA vs. TerarkDB

System Properties Comparison Interbase vs. Kinetica vs. Manticore Search 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

Multi-storage database for search, including full-text search.

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

Secondary database models

Spatial DBMS
Time Series DBMS

Time Series DBMS

using the Manticore Columnar Library

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	0.29
Rank	#302	Overall
	#21	Search engines

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

manticoresearch.com

www.sap.com/products/hana.html

github.com/bytedance/terarkdb

Technical documentation

docs.embarcadero.com/products/interbase

docs.kinetica.com

manual.manticoresearch.com

help.sap.com/hana

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Embarcadero

Kinetica

Manticore Software

SAP

ByteDance, originally Terark

Initial release

1984

2012

2017

2010

2016

Current release

InterBase 2020, December 2019

7.1, August 2021

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

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

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

Data scheme

yes

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

JDBC
ODBC

C++ API
Java API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C++
Java

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

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

Partitioning is done manually, search queries against distributed index is supported

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Source-replica replication

Synchronous replication based on Galera library

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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.