DBMS > Google Cloud Bigtable vs. Hawkular Metrics vs. Heroic vs. IRONdb

System Properties Comparison Google Cloud Bigtable vs. Hawkular Metrics vs. Heroic vs. IRONdb

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Key-value store
Wide column store

Time Series DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Website

cloud.google.com/bigtable

www.hawkular.org

github.com/spotify/heroic

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

Technical documentation

cloud.google.com/bigtable/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

spotify.github.io/heroic

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

Developer

Google

Community supported by Red Hat

Spotify

Circonus LLC.

Initial release

2015

2014

2017

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

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

C and C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

via Elasticsearch

SQL

Support of SQL

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

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HTTP REST

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API

Supported programming languages

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

Go
Java
Python
Ruby

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

Server-side scripts

Stored procedures

yes, in Lua

Triggers

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

based on Cassandra

yes

configurable replication factor, datacenter aware

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Share this page