DBMS > Google BigQuery vs. IBM Db2 vs. Splunk vs. TerminusDB vs. WakandaDB

System Properties Comparison Google BigQuery vs. IBM Db2 vs. Splunk vs. TerminusDB vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Common in IBM host environments, 2 different versions for host and Windows/Linux

Analytics Platform for Big Data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Search engine

Graph DBMS

Object oriented DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store
RDF store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/db2

www.splunk.com

terminusdb.com

wakanda.github.io

Technical documentation

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

wakanda.github.io/doc

Developer

Google

IBM

Splunk Inc.

DataChemist Ltd.

Wakanda SAS

Initial release

2010

1983

host version

2003

2018

2012

Current release

12.1, October 2016

11.0.0, January 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

free version is available

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

Open Source

AGPLv3, extended commercial license 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

C and C++

Prolog, Rust

C++, JavaScript

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

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

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

JavaScript

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

only with Windows/Unix/Linux Version

Sharding

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

Journaling Streams

none

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

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

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 journaling

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)

fine grained access rights according to SQL-standard

Access rights for users and roles

Role-based access control

yes

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.