DBMS > Apache Drill vs. Google BigQuery vs. Infobright vs. Realm vs. STSdb

System Properties Comparison Apache Drill vs. Google BigQuery vs. Infobright vs. Realm vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Large scale data warehouse service with append-only tables

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Key-value store

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	7.18
Rank	#52	Overall
	#8	Document stores

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

drill.apache.org

cloud.google.com/bigquery

ignitetech.com/softwarelibrary/infobrightdb

realm.io

github.com/STSSoft/STSdb4

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

realm.io/docs

Developer

Apache Software Foundation

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Realm, acquired by MongoDB in May 2019

STS Soft SC

Initial release

2012

2010

2005

2014

2011

Current release

1.20.3, January 2023

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPLv2, 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

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

Android
Backend: server-less
iOS
Windows

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

.NET Client API

Supported programming languages

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

In-Memory realm

User concepts

Access control

Depending on the underlying data source

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

exploiting MySQL or PostgreSQL frontend capabilities

yes

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.