DBMS > Apache Doris vs. FatDB vs. Google BigQuery vs. mSQL

System Properties Comparison Apache Doris vs. FatDB vs. Google BigQuery vs. mSQL

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

An MPP-based analytics DBMS embracing the MySQL protocol

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

Large scale data warehouse service with append-only tables

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	0.61
Rank	#235	Overall
	#110	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

cloud.google.com/bigquery

hughestech.com.au/products/msql

Technical documentation

github.com/apache/doris/wiki

cloud.google.com/bigquery/docs

Developer

Apache Software Foundation, originally contributed from Baidu

FatCloud

Google

Hughes Technologies

Initial release

2017

2012

2010

1994

Current release

1.2.2, February 2023

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free licenses can be provided

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

Server operating systems

Linux

Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
MySQL client

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

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

in JavaScript

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

none

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

none

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

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

Can implement custom security layer via applications

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.