DBMS > Google BigQuery vs. Oracle Berkeley DB vs. Spark SQL vs. TerarkDB vs. Transbase

System Properties Comparison Google BigQuery vs. Oracle Berkeley DB vs. Spark SQL vs. TerarkDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Widely used in-process key-value store

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

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

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Key-value store

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/bigquery

www.oracle.com/database/technologies/related/berkeleydb.html

spark.apache.org/sql

github.com/bytedance/terarkdb

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

Technical documentation

cloud.google.com/bigquery/docs

docs.oracle.com/cd/E17076_05/html/index.html

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

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

Developer

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

ByteDance, originally Terark

Transaction Software GmbH

Initial release

2010

1994

2014

2016

1987

Current release

18.1.40, May 2020

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache 2.0

commercial

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

C, Java, C++ (depending on the Berkeley DB edition)

Scala

C++

C and C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Java
Python
R
Scala

C++
Java

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

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

yes

Concurrency

Support for concurrent manipulation of data

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.

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.