DBMS > Google BigQuery vs. Quasardb vs. Vitess vs. YDB

System Properties Comparison Google BigQuery vs. Quasardb vs. Vitess vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Distributed, high-performance timeseries database

Scalable, distributed, cloud-native DBMS, extending MySQL

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Score	0.39
Rank	#269	Overall
	#43	Document stores
	#126	Relational DBMS

Website

cloud.google.com/bigquery

quasar.ai

vitess.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.google.com/bigquery/docs

doc.quasar.ai/master

vitess.io/docs

ydb.tech/en/docs

Developer

Google

quasardb

The Linux Foundation, PlanetScale

Yandex

Initial release

2010

2009

2013

2019

Current release

3.14.1, January 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache Version 2.0, commercial licenses available

Open Source

Apache 2.0; commercial license 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++

Server operating systems

hosted

BSD
Linux
OS X
Windows

Docker
Linux
macOS

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with selectable replication factor

Multi-source replication
Source-replica replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

Users with fine-grained authorization concept

no user groups or roles

Access rights defined for Yandex Cloud users

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.