DBMS > Brytlyt vs. FatDB vs. Google BigQuery vs. RethinkDB

System Properties Comparison Brytlyt vs. FatDB vs. Google BigQuery vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

brytlyt.io

cloud.google.com/bigquery

rethinkdb.com

Technical documentation

docs.brytlyt.io

cloud.google.com/bigquery/docs

rethinkdb.com/docs

Developer

Brytlyt

FatCloud

Google

The Linux Foundation

since July 2017

Initial release

2016

2012

2010

2009

Current release

5.0, August 2023

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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

C++

Server operating systems

Linux
OS X
Windows

Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

via applications

user defined functions

in JavaScript

Triggers

yes

via applications

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

yes

users and table-level permissions

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.