DBMS > Firebird vs. Kyligence Enterprise vs. Oracle Coherence vs. SQLite vs. Warp 10

System Properties Comparison Firebird vs. Kyligence Enterprise vs. Oracle Coherence vs. SQLite vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Firebird is an open source RDBMS forked from Borland's InterBase

A distributed analytics engine for big data, built on top of Apache Kylin

Oracles in-memory data grid solution

Widely used embeddable, in-process RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.firebirdsql.org

kyligence.io/kyligence-enterprise

www.oracle.com/java/coherence

www.sqlite.org

www.warp10.io

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.oracle.com/en/middleware/standalone/coherence

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Firebird Foundation

Kyligence, Inc.

Oracle

Dwayne Richard Hipp

SenX

Initial release

2000

As fork of Borland's InterBase

2016

2007

2000

2015

Current release

5.0.0, January 2024

14.1, August 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

Open Source

Public Domain

Open Source

Apache License 2.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

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

All OS with a Java VM

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL for queries (using Apache Calcite)

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

JCache
JPA
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API
Jupyter
WebSocket

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
C++
Java

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

PSQL

yes

WarpScript

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, with selectable consistency level

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

optionally

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

Users with fine-grained authorization concept

authentification to access the cache via certificates or http basic authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.