DBMS > Google BigQuery vs. HEAVY.AI vs. Solr vs. YDB

System Properties Comparison Google BigQuery vs. HEAVY.AI vs. Solr vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A widely used distributed, scalable search engine based on Apache Lucene

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Search engine

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

solr.apache.org

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.google.com/bigquery/docs

docs.heavy.ai

solr.apache.org/resources.html

ydb.tech/en/docs

Developer

Google

HEAVY.AI, Inc.

Apache Software Foundation

Yandex

Initial release

2010

2016

2006

2019

Current release

5.10, January 2022

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache Version 2

Open Source

Apache 2.0; commercial license 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

C++ and CUDA

Java

Server operating systems

hosted

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Java API
RESTful HTTP/JSON API

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

optimistic locking

ACID

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)

fine grained access rights according to SQL-standard

yes

Access rights defined for Yandex Cloud users

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.