DBMS > EDB Postgres vs. Google BigQuery vs. IBM Db2 vs. Splunk

System Properties Comparison EDB Postgres vs. Google BigQuery vs. IBM Db2 vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

Primary database model

Relational DBMS

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

Search engine

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

with Db2 Spatial Extender

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

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.enterprisedb.com

cloud.google.com/bigquery

www.ibm.com/products/db2

www.splunk.com

Technical documentation

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2

docs.splunk.com/Documentation/Splunk

Developer

EnterpriseDB

Google

IBM

Splunk Inc.

Initial release

2005

2010

1983

host version

2003

Current release

14, December 2021

12.1, October 2016

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

commercial

free version is available

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

C and C++

Server operating systems

Linux
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Solaris
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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard with numerous extensions

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP REST

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

.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

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

none

Sharding

only with Windows/Unix/Linux Version

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

with separate tools (MQ, InfoSphere)

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

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

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.