DBMS > Axibase vs. Google BigQuery vs. GridGain vs. Microsoft Azure Cosmos DB

System Properties Comparison Axibase vs. Google BigQuery vs. GridGain vs. Microsoft Azure Cosmos DB

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

GridGain is an in-memory computing platform, built on Apache Ignite

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Time Series DBMS

Relational DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

axibase.com/docs/atsd/finance

cloud.google.com/bigquery

www.gridgain.com

azure.microsoft.com/services/cosmos-db

Technical documentation

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

learn.microsoft.com/azure/cosmos-db

Developer

Axibase Corporation

Google

GridGain Systems, Inc.

Microsoft

Initial release

2013

2010

2007

2014

Current release

15585

GridGain 8.5.1

License

Commercial or Open Source

commercial

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

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

Java, C++, .Net

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

yes

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes

yes (cache interceptors and events)

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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)

Security Hooks for custom implementations

Access rights can be defined down to the item level

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.