DBMS > Google BigQuery vs. PlanetScale vs. SAP SQL Anywhere vs. Warp 10

System Properties Comparison Google BigQuery vs. PlanetScale vs. SAP SQL Anywhere vs. Warp 10

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

cloud.google.com/bigquery

planetscale.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.warp10.io

Technical documentation

cloud.google.com/bigquery/docs

planetscale.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.warp10.io/content/02_Getting_started

Developer

Google

PlanetScale

SAP

formerly Sybase

SenX

Initial release

2010

2020

1992

2015

Current release

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

Docker
Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
HTTP API
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Since BigQuery is designed for querying data

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

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)

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.