DBMS > BoltDB vs. Google BigQuery vs. Impala

System Properties Comparison BoltDB vs. Google BigQuery vs. Impala

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Large scale data warehouse service with append-only tables

Analytic DBMS for Hadoop

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	0.87
Rank	#228	Overall
	#35	Key-value stores

Score	53.32
Rank	#20	Overall
	#14	Relational DBMS

Score	17.59
Rank	#38	Overall
	#23	Relational DBMS

Website

github.com/boltdb/bolt

cloud.google.com/bigquery

www.cloudera.com/products/open-source/apache-hadoop/impala.html

Technical documentation

cloud.google.com/bigquery/docs

docs.cloudera.com/documentation/enterprise/latest/topics/impala.html

Developer

Google

Cloudera

Initial release

2013

2010

2013

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache Version 2

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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 DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Since BigQuery is designed for querying data

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.

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, groups and roles

based on Apache Sentry and Kerberos

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.