DBMS > Google BigQuery vs. IBM Db2 vs. Linter vs. Sphinx vs. TerarkDB

System Properties Comparison Google BigQuery vs. IBM Db2 vs. Linter vs. Sphinx vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Common in IBM host environments, 2 different versions for host and Windows/Linux

RDBMS for high security requirements

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Search engine

Key-value store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

cloud.google.com/bigquery

www.ibm.com/products/db2

linter.ru

sphinxsearch.com

github.com/bytedance/terarkdb

Technical documentation

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2

sphinxsearch.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

IBM

relex.ru

Sphinx Technologies Inc.

ByteDance, originally Terark

Initial release

2010

1983

host version

1990

2001

2016

Current release

12.1, October 2016

3.5.1, February 2023

License

Commercial or Open Source

commercial

free version is available

commercial

Open Source

GPL version 2, commercial licence available

commercial

restricted open source version 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 and C++

C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

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.

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

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Proprietary protocol

C++ API
Java API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

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.

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

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.