DBMS > Google BigQuery vs. GridGain vs. Manticore Search vs. OpenTSDB vs. VelocityDB

System Properties Comparison Google BigQuery vs. GridGain vs. Manticore Search vs. OpenTSDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Multi-storage database for search, including full-text search.

Scalable Time Series DBMS based on HBase

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Search engine

Time Series DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

cloud.google.com/bigquery

Technical documentation

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

manual.manticoresearch.com

opentsdb.net/docs/build/html/index.html

velocitydb.com/UserGuide

Developer

Google

GridGain Systems, Inc.

Manticore Software

currently maintained by Yahoo and other contributors

VelocityDB Inc

Initial release

2010

2007

2017

2011

Current release

GridGain 8.5.1

6.0, February 2023

7.x

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

LGPL

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, C++, .Net

C++

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Linux
Windows

Any that supports .NET

Data scheme

yes

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

numeric data for metrics, strings for tags

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.

yes

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

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

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

HTTP API
Telnet API

.Net

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Erlang
Go
Java
Python
R
Ruby

.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

user defined functions

Triggers

yes (cache interceptors and events)

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Synchronous replication based on Galera library

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

Based on Windows 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.