DBMS > Apache Drill vs. Brytlyt vs. GigaSpaces vs. Google BigQuery

System Properties Comparison Apache Drill vs. Brytlyt vs. GigaSpaces vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Large scale data warehouse service with append-only tables

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Secondary database models

Graph DBMS
Search engine

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

drill.apache.org

brytlyt.io

www.gigaspaces.com

cloud.google.com/bigquery

Technical documentation

drill.apache.org/docs

docs.brytlyt.io

docs.gigaspaces.com/latest/landing.html

cloud.google.com/bigquery/docs

Developer

Apache Software Foundation

Brytlyt

Gigaspaces Technologies

Google

Initial release

2012

2016

2000

2010

Current release

1.20.3, January 2023

5.0, August 2023

15.5, September 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; Commercial licenses available

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

C, C++ and CUDA

Java, C++, .Net

Server operating systems

Linux
OS X
Windows

Linux
macOS
Solaris
Windows

hosted

Data scheme

schema-free

yes

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.

yes

specific XML-type available, but no XML query functionality.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-99 for query and DML statements

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

Supported programming languages

C++

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C++
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

user defined functions

in JavaScript

Triggers

yes

yes, event driven architecture

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

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.