DBMS > Citus vs. Google BigQuery vs. IRONdb vs. Oracle NoSQL

System Properties Comparison Citus vs. Google BigQuery vs. IRONdb vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Large scale data warehouse service with append-only tables

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

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

Score	2.13
Rank	#117	Overall
	#56	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

Website

www.citusdata.com

cloud.google.com/bigquery

www.circonus.com/solutions/time-series-database/

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

docs.citusdata.com

cloud.google.com/bigquery/docs

docs.circonus.com/irondb/category/getting-started

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Google

Circonus LLC.

Oracle

Initial release

2010

2017

2011

Current release

8.1, December 2018

V0.10.20, January 2018

24.1, May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

Server operating systems

Linux

hosted

Linux

Linux
Solaris SPARC/x86

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

text, numeric, histograms

optional

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

HTTP API

RESTful HTTP API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

in JavaScript

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

configurable replication factor, datacenter aware

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

configurable

ACID within a storage node (=shard)

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.

yes

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

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.