DBMS > Google BigQuery vs. Heroic vs. Linter vs. Oracle NoSQL vs. SWC-DB

System Properties Comparison Google BigQuery vs. Heroic vs. Linter vs. Oracle NoSQL vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

RDBMS for high security requirements

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

cloud.google.com/bigquery

github.com/spotify/heroic

linter.ru

www.oracle.com/database/nosql/technologies/nosql

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

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Google

Spotify

relex.ru

Oracle

Alex Kashirin

Initial release

2010

2014

1990

2011

2020

Current release

24.1, May 2024

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

GPL V3

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 and C++

Java

C++

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Solaris SPARC/x86

Linux

Data scheme

yes

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

RESTful HTTP API

Proprietary protocol
Thrift

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C#
Go
Java
JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

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

yes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

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
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

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

off heap cache

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Access rights for users and 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.