DBMS > Google BigQuery vs. Riak TS vs. SAP HANA vs. Splunk

System Properties Comparison Google BigQuery vs. Riak TS vs. SAP HANA vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

In-memory, column based data store. Available as appliance or cloud service

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/bigquery

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/ts/latest

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

Google

Open Source, formerly Basho Technologies

SAP

Splunk Inc.

Initial release

2010

2015

2010

2003

Current release

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Server operating systems

hosted

Linux
OS X

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

yes, limited

yes

Splunk Search Processing Language for search commands

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

JDBC
ODBC

HTTP REST

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Erlang

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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.

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

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.