DBMS > BoltDB vs. Google BigQuery vs. jBASE vs. QuestDB vs. Sphinx

System Properties Comparison BoltDB vs. Google BigQuery vs. jBASE vs. QuestDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Large scale data warehouse service with append-only tables

A robust multi-value DBMS comprising development tools and middleware

A high performance open source SQL database for time series data

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Relational DBMS

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

github.com/boltdb/bolt

cloud.google.com/bigquery

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

questdb.io

sphinxsearch.com

Technical documentation

cloud.google.com/bigquery/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

questdb.io/docs

sphinxsearch.com/docs

Developer

Google

Rocket Software (formerly Zumasys)

QuestDB Technology Inc

Sphinx Technologies Inc.

Initial release

2013

2010

1991

2014

2001

Current release

5.7

3.5.1, February 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence 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

Java (Zero-GC), C++, Rust

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
Linux
Windows

Linux
macOS
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

Typing

predefined data types such as float or date

yes

optional

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

full-text index on all search fields

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

SQL with time-series extensions

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by timestamps)

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication with eventual consistency

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Since BigQuery is designed for querying data

ACID

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

through memory mapped files

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

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.