DBMS > Google BigQuery vs. SWC-DB vs. XTDB vs. Yanza

System Properties Comparison Google BigQuery vs. SWC-DB vs. XTDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service with append-only tables

A high performance, scalable Wide Column DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

cloud.google.com/bigquery

github.com/kashirin-alex/swc-db
www.swcdb.org

github.com/xtdb/xtdb
www.xtdb.com

yanza.com

Technical documentation

cloud.google.com/bigquery/docs

www.xtdb.com/docs

Developer

Google

Alex Kashirin

Juxt Ltd.

Yanza

Initial release

2010

2020

2019

2015

Current release

0.5, April 2021

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

MIT License

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Clojure

Server operating systems

hosted

Linux

All OS with a Java 8 (and higher) VM
Linux

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol
Thrift

HTTP REST
JDBC

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

Clojure
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, each node contains all data

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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)

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.