DBMS > Google BigQuery vs. OpenTSDB vs. Oracle NoSQL vs. Splunk

System Properties Comparison Google BigQuery vs. OpenTSDB vs. Oracle NoSQL 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

Scalable Time Series DBMS based on HBase

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Analytics Platform for Big Data

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Search engine

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/bigquery

opentsdb.net

www.oracle.com/database/nosql/technologies/nosql

www.splunk.com

Technical documentation

cloud.google.com/bigquery/docs

opentsdb.net/docs/build/html/index.html

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.splunk.com/Documentation/Splunk

Developer

Google

currently maintained by Yahoo and other contributors

Oracle

Splunk Inc.

Initial release

2010

2011

2003

Current release

24.1, May 2024

License

Commercial or Open Source

commercial

Open Source

LGPL

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Limited free edition and free developer edition 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

Linux
Windows

Linux
Solaris SPARC/x86

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

optional

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

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

Splunk Search Processing Language for search commands

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Telnet API

RESTful HTTP API

HTTP REST

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Erlang
Go
Java
Python
R
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual 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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

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.