DBMS > GeoSpock vs. Google BigQuery vs. IRONdb vs. Rockset

System Properties Comparison GeoSpock vs. Google BigQuery vs. IRONdb vs. Rockset

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

Spatial and temporal data processing engine for extreme data scale

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 scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Time Series DBMS

Relational DBMS
Search engine

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

geospock.com

cloud.google.com/bigquery

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

rockset.com

Technical documentation

cloud.google.com/bigquery/docs

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

docs.rockset.com

Developer

GeoSpock

Google

Circonus LLC.

Rockset

Initial release

2010

2017

2019

Current release

2.0, September 2019

V0.10.20, January 2018

License

Commercial or Open Source

commercial

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, Javascript

C and C++

C++

Server operating systems

hosted

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

temporal, categorical

all fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

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

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC

RESTful HTTP/JSON API

HTTP API

HTTP REST

Supported programming languages

.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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, in Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Automatic, metric affinity per node

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual 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

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.

User concepts

Access control

Access rights for users can be defined per table

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and organizations can be defined via Rockset console

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.