# apache/geode

Apache Geode

Repository: https://github.com/apache/geode
Canonical: https://ross.abutalabs.com/products/apache-geode
Homepage: https://geode.apache.org/
Language: Java
License: Apache-2.0
License Family: permissive
Topics: geode, datagrid, apache
Last push: 2026-08-26T14:45:17+00:00

## Health v2 (maintenance only)
Score: 90/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 74, longevity 100
- inputs: {"age_days": 4143, "days_push": 7, "days_rel": 95, "gap_med": 59, "n_releases_24m": 6}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2378, forks 693 (observed 2026-08-28T04:06:42.128923+00:00)

## What it is
Apache Geode is a distributed in-memory data management platform (originally GemFire) providing real-time, consistent, low-latency access to data across widely distributed cloud architectures. It pools memory, CPU, and network resources across processes, offering replication, partitioning, ACID transactions, OQL querying, and reliable event notifications.

## Use cases
- low-latency in-memory data grid for trading platforms
- distributed cache with replication and partitioning across a cluster
- run ACID transactions on colocated in-memory data
- query in-memory data with OQL and indexes
- build a 24x7 highly available data layer for cloud applications
- event notifications with guaranteed message delivery between services
- persist in-memory data with write-ahead logging for fast recovery

## When to choose
- you need sub-millisecond, linearly scaling reads and writes across a cluster
- you require database-like consistency and ACID transactions in an in-memory data grid
- you need elastic sharding and replication with fast parallel node recovery
- you want a mature, battle-tested platform for financial or enterprise workloads

## When to avoid
- you need a simple embedded cache where Redis or Caffeine suffices
- your dataset fits comfortably in a traditional relational database
- you want a managed cloud-native NoSQL store without self-hosted cluster operations
- your team cannot operate a JVM-based distributed cluster

## Facets
- artifact type: service
- maturity: stable
- function: database, caching, search-engine, streaming, message-queue
- domain: databases, microservices, big-data, fintech, cloud-computing
- platform: jvm, cross-platform, self-hosted
- tags: in-memory-data-grid, distributed-cache, data-grid, gemfire, oql, data-partitioning, replication, low-latency, apache, docker

## Member repositories
- apache/geode (main) score 90

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:42.128923+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:34:53.635227+00:00, confidence not recorded.
  - readme: https://github.com/apache/geode (fetched 2026-08-28T04:06:42.128923+00:00, sha 172c745f936e)
  - homepage: https://geode.apache.org/ (fetched 2026-08-29T10:15:48.357253+00:00, sha a0970c9d109e)
  - site_page: https://geode.apache.org/docs (fetched 2026-08-29T10:15:48.366818+00:00, sha 148f4a56e778)
  - site_page: https://geode.apache.org/releases (fetched 2026-08-29T10:15:48.368565+00:00, sha d8874acb8e82)
- Data as of 2026-08-30T08:39:29.467469+00:00.