DBMS > Cubrid vs. Firebird vs. Google BigQuery vs. JaguarDB vs. Splunk

System Properties Comparison Cubrid vs. Firebird vs. Google BigQuery vs. JaguarDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Search engine

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

cubrid.com (korean)
cubrid.org (english)

www.firebirdsql.org

cloud.google.com/bigquery

www.jaguardb.com

www.splunk.com

Technical documentation

cubrid.org/manuals

www.firebirdsql.org/en/reference-manuals

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

docs.splunk.com/Documentation/Splunk

Developer

CUBRID Corporation, CUBRID Foundation

Firebird Foundation

Google

DataJaguar, Inc.

Splunk Inc.

Initial release

2008

2000

As fork of Borland's InterBase

2010

2015

2003

Current release

11.0, January 2021

5.0.0, January 2024

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Initial Developer's Public License

commercial

Open Source

GPL V3.0

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++, Java

C and C++

C++

the server part. Clients available in other languages

Server operating systems

Linux
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux

Linux
OS X
Solaris
Windows

Data scheme

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

JDBC
ODBC

HTTP REST

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

PSQL

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Since BigQuery is designed for querying data

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

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.