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

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

Editorial information provided by DB-Engines

Name

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

Scalable in-memory time series database optimized for IoT and Big Data

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

Key-value store
Relational DBMS

Vector DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

cloud.google.com/bigquery

www.graphengine.io

griddb.net

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

github.com/bytedance/terarkdb

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.griddb.net

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Microsoft

Toshiba Corporation

Microsoft

ByteDance, originally Terark

Initial release

2010

2013

2015

2016

Current release

5.1, August 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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++

Server operating systems

hosted

.NET

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

RESTful HTTP API

C++ API
Java API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

C#
Java
JavaScript
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

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)

Access rights for users can be defined per database

yes

using Azure authentication

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.