DBMS > Axibase vs. Google BigQuery vs. HBase vs. OrientDB

System Properties Comparison Axibase vs. Google BigQuery vs. HBase vs. OrientDB

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

Large scale data warehouse service with append-only tables

Wide-column store based on Apache Hadoop and on concepts of BigTable

Multi-model DBMS (Document, Graph, Key/Value)

Primary database model

Time Series DBMS

Relational DBMS

Wide column store

Document store
Graph DBMS
Key-value store

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

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	3.27
Rank	#97	Overall
	#16	Document stores
	#6	Graph DBMS
	#15	Key-value stores

Website

axibase.com/docs/atsd/finance

cloud.google.com/bigquery

hbase.apache.org

orientdb.org

Technical documentation

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

www.orientdb.com/docs/last/index.html

Developer

Axibase Corporation

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

OrientDB LTD; CallidusCloud; SAP

Initial release

2013

2010

2008

2010

Current release

15585

2.3.4, January 2021

3.2.29, March 2024

License

Commercial or Open Source

commercial

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

commercial

Open Source

Apache version 2

Open Source

Apache version 2

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

Linux

hosted

Linux
Unix
Windows

using Cygwin

All OS with a Java JDK (>= JDK 6)

Data scheme

yes

schema-free, schema definition possible

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

Typing

predefined data types such as float or date

yes

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

yes

options to bring your own types, AVRO

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 query language

yes

SQL-like query language, no joins

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Coprocessors in Java

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

Single row ACID (across millions of columns)

ACID

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)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights for users and roles; record level security configurable

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.