DBMS > BigObject vs. Google BigQuery vs. Quasardb vs. SingleStore

System Properties Comparison BigObject vs. Google BigQuery vs. Quasardb vs. SingleStore

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

Large scale data warehouse service with append-only tables

Distributed, high-performance timeseries database

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

bigobject.io

cloud.google.com/bigquery

quasar.ai

www.singlestore.com

Technical documentation

docs.bigobject.io

cloud.google.com/bigquery/docs

doc.quasar.ai/master

docs.singlestore.com

Developer

BigObject, Inc.

Google

quasardb

SingleStore Inc.

Initial release

2015

2010

2009

2013

Current release

3.14.1, January 2024

8.5, January 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

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

commercial

free developer edition available

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

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

BSD
Linux
OS X
Windows

Linux

64 bit version required

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language

yes

but no triggers and foreign keys

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

by using LevelDB

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

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

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

Fine grained access control via users, groups 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.