DBMS > Interbase vs. Kdb vs. MySQL vs. SiteWhere

System Properties Comparison Interbase vs. Kdb vs. MySQL vs. SiteWhere

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

High performance Time Series DBMS

Widely used open source RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	7.73
Rank	#45	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

www.embarcadero.com/products/interbase

kx.com

www.mysql.com

github.com/sitewhere/sitewhere

Technical documentation

docs.embarcadero.com/products/interbase

code.kx.com

dev.mysql.com/doc

sitewhere1.sitewhere.io/index.html

Developer

Embarcadero

Kx Systems, a division of First Derivatives plc

Oracle

since 2010, originally MySQL AB, then Sun

SiteWhere

Initial release

1984

2000

kdb was released 2000, kdb+ in 2003

1995

2010

Current release

InterBase 2020, December 2019

3.6, May 2018

9.0.0, July 2024

License

Commercial or Open Source

commercial

free 32-bit version

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Common Public Attribution License Version 1.0

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

C and C++

Java

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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

yes

Secondary indexes

yes

table attribute 'grouped'

yes

SQL

Support of SQL

yes

SQL-like query language (q)

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

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

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

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

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

yes

proprietary syntax

Triggers

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

User concepts

Access control

fine grained access rights according to SQL-standard

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

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.