DBMS > Geode vs. GeoMesa vs. Greenplum vs. Postgres-XL

System Properties Comparison Geode vs. GeoMesa vs. Greenplum vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Key-value store

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

Technical documentation

geode.apache.org/docs

www.geomesa.org/documentation/stable/user/index.html

docs.greenplum.org

www.postgres-xl.org/documentation

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

CCRi and others

Pivotal Software Inc.

Initial release

2002

2014

2005

2014

since 2012, originally named StormDB

Current release

1.1, February 2017

4.0.5, February 2024

7.0.0, September 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Mozilla public license

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.

Implementation language

Java

Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
macOS

Data scheme

schema-free

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

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

distributed, parallel query execution

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

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

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
Java
Perl
Python
R

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

MVCC

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

depending on storage layer

User concepts

Access control

Access rights per client and object definable

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

VMware Greenplum on AWS: Parallel Postgres for Enterprise Analytics at Scale | Amazon Web Services
9 September 2019, AWS Blog

1. Introducing the Greenplum Database - Data Warehousing with Greenplum [Book]
6 December 2018, oreilly.com

RSA: EMC integrates Hadoop with Greenplum database
26 February 2013, DatacenterDynamics

Greenplum 6 ventures outside the analytic box
19 March 2019, ZDNet

Greenplum 6 review: Jack of all trades, master of some
7 November 2019, InfoWorld

provided by Google News

Share this page