Apache Geode

Overview

Build Status License Maven Central homebrew Docker Pulls Total alerts Language grade: Java Language grade: JavaScript Language grade: Python

Contents

  1. Overview
  2. How to Get Apache Geode
  3. Main Concepts and Components
  4. Location of Directions for Building from Source
  5. Geode in 5 minutes
  6. Application Development
  7. Documentation
  8. Wiki
  9. How to Contribute?
  10. Export Control

Overview

Apache Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.

Apache Geode pools memory, CPU, network resources, and optionally local disk across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques to implement high availability, improved performance, scalability, and fault tolerance. In addition to being a distributed data container, Apache Geode is an in-memory data management system that provides reliable asynchronous event notifications and guaranteed message delivery.

Apache Geode is a mature, robust technology originally developed by GemStone Systems. Commercially available as GemFireâ„¢, it was first deployed in the financial sector as the transactional, low-latency data engine used in Wall Street trading platforms. Today Apache Geode technology is used by hundreds of enterprise customers for high-scale business applications that must meet low latency and 24x7 availability requirements.

How to Get Apache Geode

You can download Apache Geode from the website, run a Docker image, or install with homebrew on OSX. Application developers can load dependencies from Maven Central.

Maven

<dependencies>
    <dependency>
        <groupId>org.apache.geode</groupId>
        <artifactId>geode-core</artifactId>
        <version>$VERSION</version>
    </dependency>
</dependencies>

Gradle

dependencies {
  compile "org.apache.geode:geode-core:$VERSION"
}

Main Concepts and Components

Caches are an abstraction that describe a node in an Apache Geode distributed system.

Within each cache, you define data regions. Data regions are analogous to tables in a relational database and manage data in a distributed fashion as name/value pairs. A replicated region stores identical copies of the data on each cache member of a distributed system. A partitioned region spreads the data among cache members. After the system is configured, client applications can access the distributed data in regions without knowledge of the underlying system architecture. You can define listeners to receive notifications when data has changed, and you can define expiration criteria to delete obsolete data in a region.

Locators provide clients with both discovery and server load balancing services. Clients are configured with locator information, and the locators maintain a dynamic list of member servers. The locators provide clients with connection information to a server.

Apache Geode includes the following features:

  • Combines redundancy, replication, and a "shared nothing" persistence architecture to deliver fail-safe reliability and performance.
  • Horizontally scalable to thousands of cache members, with multiple cache topologies to meet different enterprise needs. The cache can be distributed across multiple computers.
  • Asynchronous and synchronous cache update propagation.
  • Delta propagation distributes only the difference between old and new versions of an object (delta) instead of the entire object, resulting in significant distribution cost savings.
  • Reliable asynchronous event notifications and guaranteed message delivery through optimized, low latency distribution layer.
  • Data awareness and real-time business intelligence. If data changes as you retrieve it, you see the changes immediately.
  • Integration with Spring Framework to speed and simplify the development of scalable, transactional enterprise applications.
  • JTA compliant transaction support.
  • Cluster-wide configurations that can be persisted and exported to other clusters.
  • Remote cluster management through HTTP.
  • REST APIs for REST-enabled application development.
  • Rolling upgrades may be possible, but they will be subject to any limitations imposed by new features.

Building this Release from Source

See BUILDING.md for instructions on how to build the project.

Running Tests

See TESTING.md for instructions on how to run tests.

Geode in 5 minutes

Geode requires installation of JDK version 1.8. After installing Apache Geode, start a locator and server:

$ gfsh
gfsh> start locator
gfsh> start server

Create a region:

gfsh> create region --name=hello --type=REPLICATE

Write a client application (this example uses a Gradle build script):

build.gradle

apply plugin: 'java'
apply plugin: 'application'

mainClassName = 'HelloWorld'

repositories { mavenCentral() }
dependencies {
  compile 'org.apache.geode:geode-core:1.4.0'
  runtime 'org.slf4j:slf4j-log4j12:1.7.24'
}

src/main/java/HelloWorld.java

import java.util.Map;
import org.apache.geode.cache.Region;
import org.apache.geode.cache.client.*;

public class HelloWorld {
  public static void main(String[] args) throws Exception {
    ClientCache cache = new ClientCacheFactory()
      .addPoolLocator("localhost", 10334)
      .create();
    Region<String, String> region = cache
      .<String, String>createClientRegionFactory(ClientRegionShortcut.CACHING_PROXY)
      .create("hello");

    region.put("1", "Hello");
    region.put("2", "World");

    for (Map.Entry<String, String>  entry : region.entrySet()) {
      System.out.format("key = %s, value = %s\n", entry.getKey(), entry.getValue());
    }
    cache.close();
  }
}

Build and run the HelloWorld example:

$ gradle run

The application will connect to the running cluster, create a local cache, put some data in the cache, and print the cached data to the console:

key = 1, value = Hello
key = 2, value = World

Finally, shutdown the Geode server and locator:

gfsh> shutdown --include-locators=true

For more information see the Geode Examples repository or the documentation.

Application Development

Apache Geode applications can be written in these client technologies:

The following libraries are available external to the Apache Geode project:

Export Control

This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.

The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.

The following provides more details on the included cryptographic software:

Comments
  • Geode 8705 extensions

    Geode 8705 extensions

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by yozaner1324 66
  • Geode 8705: Introduce Classloader Isolation

    Geode 8705: Introduce Classloader Isolation

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    opened by yozaner1324 59
  • GEODE-8705: Introduce classloader isolation for deployments using JBoss Modules.

    GEODE-8705: Introduce classloader isolation for deployments using JBoss Modules.

    • introduce JarDeploymentService and ClassPathService * introduce Gradle plugin to generate module descriptors * add --enable_classloader_isolation flag to start server command * refactored DUnit tests to optionally run with classloader isolation * add checks to CI to run DUnits with classloader isolation * updated docs to reflect new Classloader isolation

    For all changes:

    • [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [x] Is your initial contribution a single, squashed commit?

    • [x] Does gradlew build run cleanly?

    • [x] Have you written or updated unit tests to verify your changes?

    • [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    windows jdk8 windows-jdk8 
    opened by yozaner1324 55
  • Geode 8705 try2 d unit

    Geode 8705 try2 d unit

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by kohlmu-pivotal 55
  • GEODE-5597 Publish geode artifacts to maven repo on GCS

    GEODE-5597 Publish geode artifacts to maven repo on GCS

    Uses vanilla maven-publish Gradle plugin, instead of nexus (nexus is still used for release artifact publishing) GCS credentials are inherited from the concourse worker

    Co-authored-by: Finn Southerland [email protected] Co-authored-by: Jake Barrett [email protected]

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [x] Is your initial contribution a single, squashed commit?

    • [x] Does gradlew build run cleanly?

    • [x] Have you written or updated unit tests to verify your changes?

    • [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by FSOUTHERLAND 27
  • RFC-0: Lightweight RFC Process

    RFC-0: Lightweight RFC Process

    This PR proposes a clearly defined decision making process for our community.

    Note that I am following the process proposed in this PR itself.

    I request that we arrive at a decision about adopting or rejecting this new process by June 20th. This should give us one week to read and discuss, which seems reasonable given the scope of the proposal.

    opened by pivotal-amurmann 26
  • GEODE-8626: Omitting field-mapping tag of cache.xml when using Simple JDBC Connector

    GEODE-8626: Omitting field-mapping tag of cache.xml when using Simple JDBC Connector

    Use the default mapping when using the Simple JDBC Connector in cache.xml and without the field-mapping tag

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [X] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [X] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [X] Is your initial contribution a single, squashed commit?

    • [X] Does gradlew build run cleanly?

    • [X] Have you written or updated unit tests to verify your changes?

    • [-] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by masaki-yamakawa 20
  • GEODE-7458: Adding option in gfsh command

    GEODE-7458: Adding option in gfsh command "start gateway sender" to control clearing of existing queues

    In this PR clearing of queue is added as option at starting of gateway sender. Also behavior of parallel and serial gateway senders are now aligned. Due to that, queue is no longer cleared at stopping of gateway sender, since we now have option whether we want it to be cleared or restored, at restarting of gateway sender.

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [*] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [*] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [*] Is your initial contribution a single, squashed commit?

    • [*] Does gradlew build run cleanly?

    • [*] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by mivanac 20
  • GEODE-9642: Wait for colocation completed at partitioned region initialization

    GEODE-9642: Wait for colocation completed at partitioned region initialization

    We have observed, that adding parallel GW sender to existing (already initialized) partitioned regions is hanging. In case command alter-region is executed (attaching GW sender to initialized region), it is hanging in cluster with more then 20 servers. Execution of command in cluster with 16 or less servers was successful, but if cluster is expanded to 20 or more, command is hanging.

    opened by mivanac 19
  • ClassLoader isolation

    ClassLoader isolation

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by kohlmu-pivotal 19
  • GEODE-8119: Threads hangs when offline disk store command is invoked

    GEODE-8119: Threads hangs when offline disk store command is invoked

    • original changes
    • the fix
    • add tests

    Thank you for submitting a contribution to Apache Geode.

    In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:

    For all changes:

    • [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [x] Is your initial contribution a single, squashed commit?

    • [x] Does gradlew build run cleanly?

    • [x] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    Note:

    Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected].

    opened by mkevo 19
  • Draft: GHA

    Draft: GHA

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    opened by sboorlagadda 0
  • Fix compile error in jdk11 due to toArray confusion

    Fix compile error in jdk11 due to toArray confusion

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    When I compile with jdk11, I got an error below: image

    This is caused by we have two toArray in PartitionedRegion, one is

    public Object[] toArray(Object[] array)
    

    other is from Collection which is introduced in jdk 11.

    default <T> T[] toArray(IntFunction<T[]> generator) {
            return toArray(generator.apply(0));
        }
    

    This PR aims to fix this.

    opened by ruanwenjun 3
  • GEODE-10401: Replace 1.15.0 with 1.15.1 as old version

    GEODE-10401: Replace 1.15.0 with 1.15.1 as old version

    Replace 1.15.0 with 1.15.1 in old versions and set as default Benchmarks baseline on develop to enable rolling upgrade tests from 1.15.1

    The serialization version has not changed between 1.15.0 and 1.15.1, so there should be no need to keep both

    opened by onichols-pivotal 0
  • Bump addressable from 2.7.0 to 2.8.1 in /geode-book

    Bump addressable from 2.7.0 to 2.8.1 in /geode-book

    Bumps addressable from 2.7.0 to 2.8.1.

    Changelog

    Sourced from addressable's changelog.

    Addressable 2.8.1

    • refactor Addressable::URI.normalize_path to address linter offenses (#430)
    • remove redundant colon in Addressable::URI::CharacterClasses::AUTHORITY regex (#438)
    • update gemspec to reflect supported Ruby versions (#466, #464, #463)
    • compatibility w/ public_suffix 5.x (#466, #465, #460)
    • fixes "invalid byte sequence in UTF-8" exception when unencoding URLs containing non UTF-8 characters (#459)
    • Ractor compatibility (#449)
    • use the whole string instead of a single line for template match (#431)
    • force UTF-8 encoding only if needed (#341)

    #460: sporkmonger/addressable#460 #463: sporkmonger/addressable#463 #464: sporkmonger/addressable#464 #465: sporkmonger/addressable#465 #466: sporkmonger/addressable#466

    Addressable 2.8.0

    • fixes ReDoS vulnerability in Addressable::Template#match
    • no longer replaces + with spaces in queries for non-http(s) schemes
    • fixed encoding ipv6 literals
    • the :compacted flag for normalized_query now dedupes parameters
    • fix broken escape_component alias
    • dropping support for Ruby 2.0 and 2.1
    • adding Ruby 3.0 compatibility for development tasks
    • drop support for rack-mount and remove Addressable::Template#generate
    • performance improvements
    • switch CI/CD to GitHub Actions
    Commits
    • 8657465 Update version, gemspec, and CHANGELOG for 2.8.1 (#474)
    • 4fc5bb6 CI: remove Ubuntu 18.04 job (#473)
    • 860fede Force UTF-8 encoding only if needed (#341)
    • 99810af Merge pull request #431 from ojab/ct-_do_not_parse_multiline_strings
    • 7ce0f48 Merge branch 'main' into ct-_do_not_parse_multiline_strings
    • 7ecf751 Merge pull request #449 from okeeblow/freeze_concatenated_strings
    • 41f12dd Merge branch 'main' into freeze_concatenated_strings
    • 068f673 Merge pull request #459 from jarthod/iso-encoding-problem
    • b4c9882 Merge branch 'main' into iso-encoding-problem
    • 08d27e8 Merge pull request #471 from sporkmonger/sporkmonger-enable-codeql
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • [DRAFT DO NOT REVIEW] Wip limit max threads to server

    [DRAFT DO NOT REVIEW] Wip limit max threads to server

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    opened by albertogpz 0
  • To test if sync writes

    To test if sync writes

    For all changes:

    • [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

    • [ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

    • [ ] Is your initial contribution a single, squashed commit?

    • [ ] Does gradlew build run cleanly?

    • [ ] Have you written or updated unit tests to verify your changes?

    • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

    opened by jvarenina 0
Releases(rel/v1.15.1)
  • rel/v1.15.1(Oct 10, 2022)

  • rel/v1.15.0(Jun 23, 2022)

    This release includes a significant number of bug fixes and improvements, including JDK17 support.

    sha256 for apache-geode-1.15.0.tgz is 97cd96e94991cbd433d93e8474e1c2e65deb92f022d810a1931464017701701b

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.15.0

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.15.0.tgz(126.33 MB)
  • rel/v1.14.4(Mar 18, 2022)

  • rel/v1.13.8(Mar 15, 2022)

  • rel/v1.12.9(Mar 10, 2022)

  • rel/v1.14.3(Jan 26, 2022)

  • rel/v1.13.7(Jan 20, 2022)

  • rel/v1.12.8(Jan 13, 2022)

  • rel/v1.14.2(Dec 16, 2021)

  • rel/v1.13.6(Dec 16, 2021)

  • rel/v1.12.7(Dec 16, 2021)

  • rel/v1.14.1(Dec 11, 2021)

  • rel/v1.13.5(Dec 11, 2021)

  • rel/v1.12.6(Dec 11, 2021)

  • rel/v1.12.5(Oct 25, 2021)

  • rel/v1.14.0(Sep 3, 2021)

    This release includes a significant number of bug fixes, improvements in current behavior along with the addition of a few statistics to monitor the cluster health.

    sha256 for apache-geode-1.14.0.tgz is d8a72225caf63889e41f8909cffc9303fb288515387f216d3207bc6d5457b947

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.0

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.14.0.tgz(130.29 MB)
  • rel/v1.13.4(Jul 30, 2021)

  • rel/v1.12.4(Jul 26, 2021)

  • rel/v1.12.3(Jun 30, 2021)

    This patch release includes a few bug fixes and dependency updates.

    sha256 for apache-geode-1.12.3.tgz is c8a59fa33a505f4dead5e687234cbaf91a19865ccd59f087da08042c8195302d

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.3

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.12.3.tgz(122.60 MB)
  • rel/v1.13.3(Jun 24, 2021)

    This patch release includes a number of bug fixes, including a fix for an issue with session state expiration.

    sha256 for apache-geode-1.13.3.tgz is c725d01336b94e4c47a921825aa1616872754def202ee1c72074156c3a3848d1

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.3

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.13.3.tgz(124.54 MB)
  • rel/v1.12.2(Apr 21, 2021)

    This patch release includes a number of bug fixes and dependency updates.

    sha256 for apache-geode-1.12.2.tgz is 89e09286eee965e18d2e1e967098bb05b5970c13e95f8fdd73c1c7f3136d8fce

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.2

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.12.2.tgz(122.55 MB)
  • rel/v1.13.2(Mar 29, 2021)

    This patch release includes a number of bug fixes, including some critical fixes if upgrading from an earlier version of Geode.

    sha256 for apache-geode-1.13.2.tgz is bc2d2e9bcec8f2fdfa2419894962314a3e3569fa617c3e2f6beca8097197ad02

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.2

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.13.2.tgz(124.45 MB)
  • rel/v1.12.1(Feb 26, 2021)

    This patch release includes a large number of bug fixes, including some critical fixes if using TLS communication.

    sha256 for apache-geode-1.12.1.tgz is b7ab42433712ba52175393fae6614862e55f38516bd209cb2e54c1689afaf070

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.1

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.12.1.tgz(122.21 MB)
  • rel/v1.13.1(Nov 18, 2020)

    This patch release includes a number of bug fixes, including some critical fixes if using TLS communication.

    sha256 for apache-geode-1.13.1.tgz is 3239522afee932e0a06246b2b4130bc8a5cbae71aa5244cc4dcb24d4329044c3

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.1

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.13.1.tgz(123.87 MB)
  • rel/v1.13.0(Nov 12, 2020)

    This release contains some new gfsh commands and support for SNI as well as a number of improvements and bug fixes.

    sha256 for apache-geode-1.13.0.tgz is 8caf6dcafa5c6bb7c10dc7d512d0569dd16e463e01c18997118e20a5f43e6097

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.0

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.13.0.tgz(123.79 MB)
  • rel/v1.12.0(Nov 12, 2020)

    This release contains a new OQL security framework as well as a number of improvements and bug fixes.

    sha256 for apache-geode-1.12.0.tgz is 063b473dac914aca53c09326487cc96c63ef84eecc8b053c8cc3d5110e82f179

    See full release notes at https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.0

    Source code(tar.gz)
    Source code(zip)
    apache-geode-1.12.0.tgz(122.14 MB)
Owner
The Apache Software Foundation
The Apache Software Foundation
Mirror of Apache Storm

Master Branch: Storm is a distributed realtime computation system. Similar to how Hadoop provides a set of general primitives for doing batch processi

The Apache Software Foundation 6.4k Dec 26, 2022
Apache Mesos is a cluster manager that provides efficient resource isolation and sharing across distributed applications, or frameworks

Apache Mesos is a cluster manager that provides efficient resource isolation and sharing across distributed applications, or frameworks. It can run Hadoop, Jenkins, Spark, Aurora, and other frameworks on a dynamically shared pool of nodes.

The Apache Software Foundation 5k Dec 31, 2022
Oryx 2: Lambda architecture on Apache Spark, Apache Kafka for real-time large scale machine learning

Oryx 2 is a realization of the lambda architecture built on Apache Spark and Apache Kafka, but with specialization for real-time large scale machine l

Oryx Project 1.8k Dec 28, 2022
Oryx 2: Lambda architecture on Apache Spark, Apache Kafka for real-time large scale machine learning

Oryx 2 is a realization of the lambda architecture built on Apache Spark and Apache Kafka, but with specialization for real-time large scale machine l

Oryx Project 1.7k Mar 12, 2021
Oryx 2: Lambda architecture on Apache Spark, Apache Kafka for real-time large scale machine learning

Oryx 2 is a realization of the lambda architecture built on Apache Spark and Apache Kafka, but with specialization for real-time large scale machine l

Oryx Project 1.8k Dec 28, 2022
Equivalent Exchange 3 Apache 2 Equivalent Exchange 3 pahimar Equivalent-Exchange-3. Mods for Minecraft. License: Apache 2 , .

Welcome to Equivalent Exchange 3! All versions are available here Minecraft Forums page Compiling EE3 - For those that want the latest unreleased feat

Rob Davis 709 Dec 15, 2022
Apache Solr is an enterprise search platform written in Java and using Apache Lucene.

Apache Solr is an enterprise search platform written in Java and using Apache Lucene. Major features include full-text search, index replication and sharding, and result faceting and highlighting.

The Apache Software Foundation 630 Dec 28, 2022
FLiP: StreamNative: Cloud-Native: Streaming Analytics Using Apache Flink SQL on Apache Pulsar

StreamingAnalyticsUsingFlinkSQL FLiP: StreamNative: Cloud-Native: Streaming Analytics Using Apache Flink SQL on Apache Pulsar Running on NVIDIA XAVIER

Timothy Spann 5 Dec 19, 2021
Apache Cayenne is an open source persistence framework licensed under the Apache License

Apache Cayenne is an open source persistence framework licensed under the Apache License, providing object-relational mapping (ORM) and remoting services.

The Apache Software Foundation 284 Dec 31, 2022
Spark-Crawler: Apache Nutch-like crawler that runs on Apache Spark.

Sparkler A web crawler is a bot program that fetches resources from the web for the sake of building applications like search engines, knowledge bases

USC Information Retrieval & Data Science 396 Dec 17, 2022
Apache ORC - the smallest, fastest columnar storage for Hadoop workloads

Apache ORC ORC is a self-describing type-aware columnar file format designed for Hadoop workloads. It is optimized for large streaming reads, but with

The Apache Software Foundation 576 Jan 2, 2023
Apache Calcite

Apache Calcite Apache Calcite is a dynamic data management framework. It contains many of the pieces that comprise a typical database management syste

The Apache Software Foundation 3.6k Dec 31, 2022
Apache Druid: a high performance real-time analytics database.

Website | Documentation | Developer Mailing List | User Mailing List | Slack | Twitter | Download Apache Druid Druid is a high performance real-time a

The Apache Software Foundation 12.3k Jan 1, 2023
Mirror of Apache Deltaspike

Apache DeltaSpike Documentation Mailing Lists Contribution Guide JIRA Apache License v2.0 Apache DeltaSpike is a suite of portable CDI Extensions inte

The Apache Software Foundation 141 Jan 1, 2023
Apache Wicket - Component-based Java web framework

What is Apache Wicket? Apache Wicket is an open source, java, component based, web application framework. With proper mark-up/logic separation, a POJO

The Apache Software Foundation 657 Dec 31, 2022
Apache Dubbo is a high-performance, java based, open source RPC framework.

Apache Dubbo Project Apache Dubbo is a high-performance, Java-based open-source RPC framework. Please visit official site for quick start and document

The Apache Software Foundation 38.3k Jan 9, 2023
A high performance replicated log service. (The development is moved to Apache Incubator)

Apache DistributedLog (incubating) Apache DistributedLog (DL) is a high-throughput, low-latency replicated log service, offering durability, replicati

Twitter 2.2k Dec 29, 2022
The Apache Software Foundation 3k Jan 4, 2023