DBMS > BigObject vs. Google BigQuery vs. IRONdb vs. Titan

System Properties Comparison BigObject vs. Google BigQuery vs. IRONdb vs. Titan

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.

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Analytic DBMS for real-time computations and queries

Large scale data warehouse service with append-only tables

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Time Series DBMS

Graph DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

bigobject.io

cloud.google.com/bigquery

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

github.com/thinkaurelius/titan

Technical documentation

docs.bigobject.io

cloud.google.com/bigquery/docs

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

github.com/thinkaurelius/titan/wiki

Developer

BigObject, Inc.

Google

Circonus LLC.

Aurelius, owned by DataStax

Initial release

2015

2010

2017

2012

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Apache license, version 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

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

hosted

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

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

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Relationships in graph

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

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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)

User authentification and security via Rexster Graph Server

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.