DBMS > Google BigQuery vs. PlanetScale vs. RDF4J vs. Sequoiadb

System Properties Comparison Google BigQuery vs. PlanetScale vs. RDF4J vs. Sequoiadb

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

RDF store

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

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

Website

cloud.google.com/bigquery

planetscale.com

rdf4j.org

www.sequoiadb.com

Technical documentation

cloud.google.com/bigquery/docs

planetscale.com/docs

rdf4j.org/documentation

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

Developer

Google

PlanetScale

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Sequoiadb Ltd.

Initial release

2010

2020

2004

2013

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

hosted

Docker
Linux
macOS

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

with proprietary extensions

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol using JSON

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

Java
PHP
Python

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

yes

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency across shards
Immediate Consistency within a shard

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

ACID

Isolation support depends on the API used

Document is locked during a transaction

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 storage is supported as well

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

simple password-based access control

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.