DBMS > Geode vs. Heroic vs. Percona Server for MongoDB vs. searchxml

System Properties Comparison Geode vs. Heroic vs. Percona Server for MongoDB vs. searchxml

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Key-value store

Time Series DBMS

Document store

Native XML DBMS
Search engine

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

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

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	0.55
Rank	#253	Overall
	#39	Document stores

Score	0.01
Rank	#386	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

geode.apache.org

github.com/spotify/heroic

www.percona.com/mongodb/software/percona-server-for-mongodb

www.searchxml.net/category/products

Technical documentation

geode.apache.org/docs

spotify.github.io/heroic

docs.percona.com/percona-distribution-for-mongodb

www.searchxml.net/support/handouts

Developer

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

Spotify

Percona

informationpartners gmbh

Initial release

2002

2014

2015

Current release

1.1, February 2017

3.4.10-2.10, November 2017

1.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

GPL Version 2

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.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Windows

Data scheme

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language (OQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

proprietary protocol using JSON

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

on the application server

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

multiple readers, single writer

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

via In-Memory Engine

User concepts

Access control

Access rights per client and object definable

Access rights for users and roles

Domain, group and role-based access control at the document level and for application services

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

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

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

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven ...
30 June 2018, InfoQ.com

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

How to Plan Your MongoDB Upgrade
29 January 2024, The New Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

Is database-as-a-service in Percona's future?
23 May 2022, VentureBeat

provided by Google News

Share this page