DBMS > Google BigQuery vs. TimescaleDB vs. Titan vs. Warp 10

System Properties Comparison Google BigQuery vs. TimescaleDB vs. Titan vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Large scale data warehouse service with append-only tables

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Titan is a Graph DBMS optimized for distributed clusters.

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

cloud.google.com/bigquery

www.timescale.com

github.com/thinkaurelius/titan

www.warp10.io

Technical documentation

cloud.google.com/bigquery/docs

docs.timescale.com

github.com/thinkaurelius/titan/wiki

www.warp10.io/content/02_Getting_started

Developer

Google

Timescale

Aurelius, owned by DataStax

SenX

Initial release

2010

2017

2012

2015

Current release

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache license, version 2.0

Open Source

Apache License 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

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, across time and space (hash partitioning) attributes

yes

via pluggable storage backends

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with hot standby and reads on replicas

yes

selectable replication factor

based on HBase

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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

Durability

Support for making data persistent

yes

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

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

User authentification and security via Rexster Graph Server

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.