DBMS > BoltDB vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Sphinx

System Properties Comparison BoltDB vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Key-value store

Relational DBMS

Graph DBMS
Key-value store

Search engine

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

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

github.com/boltdb/bolt

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

cloud.google.com/bigquery

www.graphengine.io

sphinxsearch.com

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

sphinxsearch.com/docs

Developer

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Sphinx Technologies Inc.

Initial release

2013

2008

2010

2001

Current release

11.0, January 2021

3.5.1, February 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

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

C, C++, Java

.NET and C

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

hosted

.NET

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

Proprietary protocol

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

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

yes

Transaction concepts

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

yes

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

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.