DBMS > Google BigQuery vs. Realm vs. Splice Machine vs. STSdb vs. Teradata Aster

System Properties Comparison Google BigQuery vs. Realm vs. Splice Machine vs. STSdb vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Platform for big data analytics on multistructured data sources and types

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

cloud.google.com/bigquery

realm.io

splicemachine.com

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/bigquery/docs

realm.io/docs

splicemachine.com/how-it-works

Developer

Google

Realm, acquired by MongoDB in May 2019

Splice Machine

STS Soft SC

Teradata

Initial release

2010

2014

2011

2005

Current release

3.1, March 2021

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

AGPL 3.0, commercial license available

Open Source

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

Java

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
OS X
Solaris
Windows

Windows

Linux

Data scheme

yes

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

.NET Client API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.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

C#
Java

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

runs within the applications so server-side scripts are unnecessary

yes

Java

R packages

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

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

yes, multi-version concurrency control (MVCC)

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

In-Memory realm

yes

User concepts

Access control

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

fine grained access rights 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.