DBMS > Google BigQuery vs. IBM Cloudant vs. Sequoiadb vs. Spark SQL vs. Transbase

System Properties Comparison Google BigQuery vs. IBM Cloudant vs. Sequoiadb vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Database as a Service offering based on Apache CouchDB

NewSQL database with distributed OLTP and SQL

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

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

Primary database model

Relational DBMS

Document store

Document store
Relational DBMS

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/cloudant

www.sequoiadb.com

spark.apache.org/sql

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

Technical documentation

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

www.sequoiadb.com/en/index.php?m=Files&a=index

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

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

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Sequoiadb Ltd.

Apache Software Foundation

Transaction Software GmbH

Initial release

2010

2013

2014

1987

Current release

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.0

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

Erlang

C++

Scala

C and C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

yes

SQL-like query language

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

proprietary protocol using JSON

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C++
Java
PHP
Python

Java
Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

atomic operations within a document possible

Document is locked during a transaction

yes

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

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 can be defined per database

simple password-based access control

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.