DBMS > BigObject vs. Faircom DB vs. Google BigQuery vs. Heroic

System Properties Comparison BigObject vs. Faircom DB vs. Google BigQuery vs. Heroic

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Large scale data warehouse service with append-only tables

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

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

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Website

bigobject.io

www.faircom.com/products/faircom-db

cloud.google.com/bigquery

github.com/spotify/heroic

Technical documentation

docs.bigobject.io

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

cloud.google.com/bigquery/docs

spotify.github.io/heroic

Developer

BigObject, Inc.

FairCom Corporation

Google

Spotify

Initial release

2015

1979

2010

2014

Current release

V13, July 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

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

ANSI C, C++

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

via Elasticsearch

SQL

Support of SQL

SQL-like DML and DDL statements

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

RESTful HTTP/JSON API

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

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

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

yes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

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.