DBMS > Elasticsearch vs. Google BigQuery vs. Greenplum vs. IBM Db2

System Properties Comparison Elasticsearch vs. Google BigQuery vs. Greenplum vs. IBM Db2

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Large scale data warehouse service with append-only tables

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

Primary database model

Search engine

Relational DBMS

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

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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	132.83
Rank	#7	Overall
	#1	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Website

www.elastic.co/elasticsearch

cloud.google.com/bigquery

greenplum.org

www.ibm.com/products/db2

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/bigquery/docs

docs.greenplum.org

www.ibm.com/docs/en/db2

Developer

Elastic

Google

Pivotal Software Inc.

IBM

Initial release

2010

2005

1983

host version

Current release

8.6, January 2023

7.0.0, September 2023

12.1, October 2016

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

Apache 2.0

commercial

free version is 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

C and C++

Server operating systems

All OS with a Java VM

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

since Version 4.2

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

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

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

only with Windows/Unix/Linux Version

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

with separate tools (MQ, InfoSphere)

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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.

Memcached and Redis integration

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

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.