DBMS > Axibase vs. Cubrid vs. Google BigQuery vs. Google Cloud Datastore vs. Graph Engine

System Properties Comparison Axibase vs. Cubrid vs. Google BigQuery vs. Google Cloud Datastore vs. Graph Engine

Editorial information provided by DB-Engines

Name

Description

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Primary database model

Time Series DBMS

Relational DBMS

Document store

Graph DBMS
Key-value store

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Website

axibase.com/docs/atsd/finance

cubrid.com (korean)
cubrid.org (english)

cloud.google.com/bigquery

cloud.google.com/datastore

www.graphengine.io

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

www.graphengine.io/docs/manual

Developer

Axibase Corporation

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Initial release

2013

2008

2010

2008

2010

Current release

15585

11.0, January 2021

License

Commercial or Open Source

commercial

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

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

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, C++, Java

.NET and C

Server operating systems

Linux

Linux
Windows

hosted

.NET

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

yes, details here

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 (GQL)

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

yes

Java Stored Procedures

user defined functions

in JavaScript

using Google App Engine

yes

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.