DBMS > Google BigQuery vs. Spark SQL vs. Sphinx vs. Splice Machine vs. Transbase

System Properties Comparison Google BigQuery vs. Spark SQL vs. Sphinx vs. Splice Machine vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

cloud.google.com/bigquery

spark.apache.org/sql

sphinxsearch.com

splicemachine.com

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

spark.apache.org/docs/latest/sql-programming-guide.html

sphinxsearch.com/docs

splicemachine.com/how-it-works

www.transaction.de/en/products/transbase/features.html

Developer

Google

Apache Software Foundation

Sphinx Technologies Inc.

Splice Machine

Transaction Software GmbH

Initial release

2010

2014

2001

2014

1987

Current release

3.5.0 ( 2.13), September 2023

3.5.1, February 2023

3.1, March 2021

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

commercial

free development license

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

Scala

C++

Java

C and C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

SQL-like query language (SphinxQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Python
R
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

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

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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)

Access rights for users, groups and roles according to SQL-standard

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.