DBMS > Amazon Redshift vs. Google BigQuery vs. Realm vs. Splice Machine

System Properties Comparison Amazon Redshift vs. Google BigQuery vs. Realm vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Large scale data warehouse service with append-only tables

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

aws.amazon.com/redshift

cloud.google.com/bigquery

realm.io

splicemachine.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/bigquery/docs

realm.io/docs

splicemachine.com/how-it-works

Developer

Amazon (based on PostgreSQL)

Google

Realm, acquired by MongoDB in May 2019

Splice Machine

Initial release

2012

2010

2014

Current release

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

AGPL 3.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

Java

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
OS X
Solaris
Windows

Data scheme

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

in JavaScript

runs within the applications so server-side scripts are unnecessary

yes

Java

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

In-Memory realm

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

yes

Access rights for users, groups and roles according to SQL-standard

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.