DBMS > CockroachDB vs. Firebird vs. SAP HANA vs. Splunk

System Properties Comparison CockroachDB vs. Firebird vs. SAP HANA vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

In-memory, column based data store. Available as appliance or cloud service

Analytics Platform for Big Data

Primary database model

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.cockroachlabs.com

www.firebirdsql.org

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

www.cockroachlabs.com/docs

www.firebirdsql.org/en/reference-manuals

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

Cockroach Labs

Firebird Foundation

SAP

Splunk Inc.

Initial release

2015

2000

As fork of Borland's InterBase

2010

2003

Current release

23.1.1, May 2023

5.0.0, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Initial Developer's Public License

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Server operating systems

Linux
macOS
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

dynamic schema

yes

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, wire compatible with PostgreSQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC

HTTP REST

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

PSQL

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

yes

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

User concepts

Access control

Role-based access control

Users with fine-grained authorization concept

yes

Access rights for users and roles

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.