DBMS > Axibase vs. Badger vs. Google BigQuery vs. HEAVY.AI

System Properties Comparison Axibase vs. Badger vs. Google BigQuery vs. HEAVY.AI

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/dgraph-io/badger

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

godoc.org/github.com/dgraph-io/badger

cloud.google.com/bigquery/docs

docs.heavy.ai

Developer

Axibase Corporation

DGraph Labs

Google

HEAVY.AI, Inc.

Initial release

2013

2017

2010

2016

Current release

15585

5.10, January 2022

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; enterprise edition available

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 CUDA

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate 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.

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

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.