DBMS > Graph Engine vs. Interbase vs. Kdb vs. SQLite

System Properties Comparison Graph Engine vs. Interbase vs. Kdb vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Light-weight proven RDBMS

originally from Borland

High performance Time Series DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

www.embarcadero.com/products/interbase

kx.com

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

docs.embarcadero.com/products/interbase

code.kx.com

www.sqlite.org/docs.html

Developer

Microsoft

Embarcadero

Kx Systems, a division of First Derivatives plc

Dwayne Richard Hipp

Initial release

2010

1984

2000

kdb was released 2000, kdb+ in 2003

2000

Current release

InterBase 2020, December 2019

3.6, May 2018

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

free 32-bit version

Open Source

Public Domain

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

.NET and C

Server operating systems

.NET

Android
iOS
Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

Secondary indexes

yes

table attribute 'grouped'

yes

SQL

Support of SQL

yes

SQL-like query language (q)

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

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

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

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

via file-system locks

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

rights management via user accounts

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.