DBMS > FatDB vs. Google BigQuery vs. Quasardb vs. Stardog

System Properties Comparison FatDB vs. Google BigQuery vs. Quasardb vs. Stardog

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

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

Large scale data warehouse service with append-only tables

Distributed, high-performance timeseries database

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Graph DBMS
RDF store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

cloud.google.com/bigquery

quasar.ai

www.stardog.com

Technical documentation

cloud.google.com/bigquery/docs

doc.quasar.ai/master

docs.stardog.com

Developer

FatCloud

Google

quasardb

Stardog-Union

Initial release

2012

2010

2009

2010

Current release

3.14.1, January 2024

7.3.0, May 2020

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

Windows

hosted

BSD
Linux
OS X
Windows

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes

integer and binary

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.

Import/export of XML data possible

Secondary indexes

yes

with tags

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-like query language

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

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

RESTful HTTP/JSON API

HTTP API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

user defined functions

in JavaScript

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via applications

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication with selectable replication factor

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

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.