DBMS > Google BigQuery vs. Splunk vs. STSdb vs. Teradata Aster vs. TigerGraph

System Properties Comparison Google BigQuery vs. Splunk vs. STSdb vs. Teradata Aster vs. TigerGraph

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

Analytics Platform for Big Data

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

cloud.google.com/bigquery

www.splunk.com

github.com/STSSoft/STSdb4

www.tigergraph.com

Technical documentation

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

docs.tigergraph.com

Developer

Google

Splunk Inc.

STS Soft SC

Teradata

Initial release

2010

2003

2011

2005

2017

Current release

4.0.8, September 2015

License

Commercial or Open Source

commercial

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

C++

Server operating systems

hosted

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

yes

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

Splunk Search Processing Language for search commands

yes

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP REST

.NET Client API

ADO.NET
JDBC
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

R packages

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source 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

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

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

ACID

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.

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

fine grained access rights according to SQL-standard

Role-based access control

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.