DBMS > Brytlyt vs. Google BigQuery vs. Heroic vs. Linter vs. SWC-DB

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

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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 high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

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	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

brytlyt.io

cloud.google.com/bigquery

github.com/spotify/heroic

linter.ru

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

Technical documentation

docs.brytlyt.io

cloud.google.com/bigquery/docs

spotify.github.io/heroic

Developer

Brytlyt

Google

Spotify

relex.ru

Alex Kashirin

Initial release

2016

2010

2014

1990

2020

Current release

5.0, August 2023

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

C, C++ and CUDA

Java

C and C++

C++

Server operating systems

Linux
OS X
Windows

hosted

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

Linux

Data scheme

yes

schema-free

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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)

Proprietary protocol
Thrift

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C++

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

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

Source-replica replication

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

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.

User concepts

Access control

fine grained access rights according to SQL-standard

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

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.