DBMS > Greenplum vs. GridDB vs. OpenSearch vs. Oracle Coherence

System Properties Comparison Greenplum vs. GridDB vs. OpenSearch vs. Oracle Coherence

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Scalable in-memory time series database optimized for IoT and Big Data

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Oracles in-memory data grid solution

Primary database model

Secondary database models

Document store
Spatial DBMS

Key-value store
Relational DBMS

Vector DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

greenplum.org

griddb.net

github.com/opensearch-project
opensearch.org

www.oracle.com/java/coherence

Technical documentation

docs.greenplum.org

docs.griddb.net

opensearch.org/docs/latest

docs.oracle.com/en/middleware/standalone/coherence

Developer

Pivotal Software Inc.

Toshiba Corporation

Amazon Web Services

Oracle

Initial release

2005

2013

2021

2007

Current release

7.0.0, September 2023

5.1, August 2022

2.5.0, January 2023

14.1, August 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++

Java

Server operating systems

Linux

All OS with a Java VM

Data scheme

yes

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

JCache
JPA
RESTful HTTP API

Supported programming languages

C
Java
Perl
Python
R

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

authentification to access the cache via certificates or http basic authentication

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.