DBMS > Google BigQuery vs. Graph Engine vs. IRONdb vs. Microsoft Azure AI Search vs. TerarkDB

System Properties Comparison Google BigQuery vs. Graph Engine vs. IRONdb vs. Microsoft Azure AI Search vs. TerarkDB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service with append-only tables

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

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

Search-as-a-service for web and mobile app development

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Search engine

Key-value store

Secondary database models

Vector DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

cloud.google.com/bigquery

www.graphengine.io

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

azure.microsoft.com/en-us/services/search

github.com/bytedance/terarkdb

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

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

learn.microsoft.com/en-us/azure/search

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Microsoft

Circonus LLC.

Microsoft

ByteDance, originally Terark

Initial release

2010

2017

2015

2016

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

restricted open source version 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

.NET and C

C and C++

C++

Server operating systems

hosted

.NET

Linux

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

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

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

HTTP API

RESTful HTTP API

C++ API
Java API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

C#
Java
JavaScript
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

yes, in Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

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

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

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)

yes

using Azure authentication

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.