DBMS > BoltDB vs. Firebird vs. Kinetica vs. MarkLogic vs. RocksDB

System Properties Comparison BoltDB vs. Firebird vs. Kinetica vs. MarkLogic vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Fully vectorized database across both GPUs and CPUs

Operational and transactional Enterprise NoSQL database

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

Primary database model

Key-value store

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

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

Website

github.com/boltdb/bolt

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.kinetica.com

docs.marklogic.com

github.com/facebook/rocksdb/wiki

Developer

Firebird Foundation

Kinetica

MarkLogic Corp.

Facebook, Inc.

Initial release

2013

2000

As fork of Borland's InterBase

2012

2001

2013

Current release

5.0.0, January 2024

7.1, August 2021

11.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Initial Developer's Public License

commercial

restricted free version is available

Open Source

BSD

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++

C, C++

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

schema-free

Schema can be enforced

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL92

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

C++ API
Java API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

PSQL

user defined functions

yes

via XQuery or JavaScript

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

ACID

can act as a resource manager in an XA/JTA transaction

yes

Concurrency

Support for concurrent manipulation of data

yes

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

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

GPU vRAM or System RAM

yes, with Range Indexes

yes

User concepts

Access control

Users with fine-grained authorization concept

Access rights for users and roles on table level

Role-based access control at the document and subdocument levels

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.