DBMS > Interbase vs. Lovefield vs. RocksDB vs. TerarkDB

System Properties Comparison Interbase vs. Lovefield vs. RocksDB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

Embeddable relational database for web apps written in pure JavaScript

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.embarcadero.com/products/interbase

google.github.io/lovefield

rocksdb.org

github.com/bytedance/terarkdb

Technical documentation

docs.embarcadero.com/products/interbase

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Embarcadero

Google

Facebook, Inc.

ByteDance, originally Terark

Initial release

1984

2014

2013

2016

Current release

InterBase 2020, December 2019

2.1.12, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

JavaScript

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

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 query language

via JavaScript builder pattern

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

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

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

Triggers

yes

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

none

yes

none

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.