DBMS > Google BigQuery vs. Machbase Neo vs. PlanetScale

System Properties Comparison Google BigQuery vs. Machbase Neo vs. PlanetScale

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

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Relational DBMS

Time Series DBMS

Relational 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	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

cloud.google.com/bigquery

machbase.com

planetscale.com

Technical documentation

cloud.google.com/bigquery/docs

machbase.com/dbms

planetscale.com/docs

Developer

Google

Machbase

PlanetScale

Initial release

2010

2013

2020

Current release

V8.0, August 2023

License

Commercial or Open Source

commercial

free test version available

commercial

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

Server operating systems

hosted

Linux
macOS
Windows

Docker
Linux
macOS

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

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
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

Eventual Consistency across shards
Immediate Consistency within a shard

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

volatile and lookup table

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

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.