DBMS > Geode vs. Heroic vs. Manticore Search vs. PostGIS

System Properties Comparison Geode vs. Heroic vs. Manticore Search vs. PostGIS

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

Multi-storage database for search, including full-text search.

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational 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.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

geode.apache.org

github.com/spotify/heroic

manticoresearch.com

postgis.net

Technical documentation

geode.apache.org/docs

spotify.github.io/heroic

manual.manticoresearch.com

postgis.net/documentation

Developer

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

Spotify

Manticore Software

Initial release

2002

2014

2017

2005

Current release

1.1, February 2017

6.0, February 2023

3.4.2, February 2024

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

Open Source

GPL v2.0

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

FreeBSD
Linux
macOS
Windows

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

via Elasticsearch

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Synchronous replication based on Galera library

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate 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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

yes

based on PostgreSQL

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

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

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, oreilly.com

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

provided by Google News

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

provided by Google News

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

Google's Gemini comes to databases
9 April 2024, Yahoo Canada Shine On

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

provided by Google News

Share this page