DBMS > Google BigQuery vs. Infobright vs. NSDb vs. SwayDB

System Properties Comparison Google BigQuery vs. Infobright vs. NSDb vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	0.04
Rank	#373	Overall
	#57	Key-value stores

Website

cloud.google.com/bigquery

ignitetech.com/softwarelibrary/infobrightdb

nsdb.io

swaydb.simer.au

Technical documentation

cloud.google.com/bigquery/docs

nsdb.io/Architecture

Developer

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Simer Plaha

Initial release

2010

2005

2017

2018

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache Version 2.0

Open Source

GNU Affero GPL V3.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

Java, Scala

Scala

Server operating systems

hosted

Linux
Windows

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

Knowledge Grid Technology used instead

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Scala

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.