DBMS > FatDB vs. Google BigQuery vs. Infobright vs. Splunk vs. Teradata Aster

System Properties Comparison FatDB vs. Google BigQuery vs. Infobright vs. Splunk vs. Teradata Aster

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Analytics Platform for Big Data

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/bigquery

ignitetech.com/softwarelibrary/infobrightdb

www.splunk.com

Technical documentation

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

Developer

FatCloud

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Splunk Inc.

Teradata

Initial release

2012

2010

2005

2003

2005

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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

Server operating systems

Windows

hosted

Linux
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

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

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

via applications

user defined functions

in JavaScript

yes

R packages

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Multi-source replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

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

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.

yes

User concepts

Access control

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles

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.