DBMS > Geode vs. GridGain vs. Postgres-XL vs. STSdb

System Properties Comparison Geode vs. GridGain vs. Postgres-XL vs. STSdb

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

GridGain is an in-memory computing platform, built on Apache Ignite

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

geode.apache.org

www.gridgain.com

www.postgres-xl.org

github.com/STSSoft/STSdb4

Technical documentation

geode.apache.org/docs

www.gridgain.com/docs/index.html

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.

GridGain Systems, Inc.

STS Soft SC

Initial release

2002

2007

2014

since 2012, originally named StormDB

2011

Current release

1.1, February 2017

GridGain 8.5.1

10 R1, October 2018

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Mozilla public license

Open Source

GPLv2, commercial license available

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

Java, C++, .Net

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

Linux
macOS

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

ANSI-99 for query and DML statements, subset of DDL

yes

distributed, parallel query execution

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

.NET Client API

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

C#
Java

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

User concepts

Access control

Access rights per client and object definable

Security Hooks for custom implementations

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

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

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

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

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

GridGain Named in the 2023 Gartner® Market Guide for Event Stream Processing
22 August 2023, GlobeNewswire

GridGain to Sponsor, Exhibit at Kafka Summit 2024 in London
12 March 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

provided by Google News

Share this page