Greetings Spring Community!

It is my pleasure to announce the first milestone release of both Spring Session Data Geode for Apache Geode and Spring Session Session Data GemFire for Pivotal GemFire.

Both artifacts can be downloaded from Spring’s libs-milestone Repository using Maven …​

  <dependency>
    <groupId>org.springframework.session</groupId>
    <artifactId>spring-session-data-geode</artifactId>
    <version>2.0.0.M1</version>
  </dependency>

Or with Gradle…​

  compile 'org.springframework.session:spring-session-data-geode:2.0.0.M1'

To use Spring Session with Pivotal GemFire, just switch the artifact from spring-session-data-geode to spring-session-data-gemfire.

Backstory

Sometime ago, @rob_winch, Spring Session Core creator and project lead, reorganized the Spring Session project by breaking out previously supported data stores into separate modules.

The primary driver for this split was to enable supported Spring Session data store providers to progress independently based on both the community’s as well as customer needs.

Well, Pivotal GemFire was 1 of the supported data stores that was separated from the core Spring Session project. Along with Pivotal GemFire, support for Apache Geode was also under development.

So today rounds out the supported Spring Session data stores to now officially include Apache Geode and Pivotal GemFire, in addition to Redis, MongoDB, JDBC, and Hazelcast, in the 2.0 release line.

In The Release

Both Spring Session Data Geode and Spring Session Data GemFire include the following improvements…​

• Compatible with Spring Framework 5.0.0.RC3.

• Runs with Spring Boot 2.0.0.M2.

• Based on Spring Session core 2.0.0.M3.

• Based on Spring Data Kay RC2, which includes _Spring Data Geode 2.0.0.RC2 and _Spring Data GemFire 2.0.0.RC2.

• Based on Apache Geode 1.2.0 and Pivotal GemFire 9.1.0, respectively.

• Revised documentation.

• Greatly simplified configuration using Spring Data Geode/GemFire’s new Annotation based configuration model. See the samples.

For instance, to build a Spring Boot application that uses Spring Session Data Geode to manage the HttpSession, all a developer need do is…​

@SpringBootApplication
@ClientCacheApplication
@EnableGemFireHttpSession
class MyApplication {

  public static void main(String[] args) {
    SpringApplication.run(MyApplication.class, args);
  }
}

Both, Spring Data Geode’s @ClientCacheApplication and Spring Session Data Geode’s @EnableGemFireHttpSession annotations are all that are needed to turn your Spring Boot application into a Geode cache client capable of managing the HTTP Session state by distributing data to a cluster of Geode servers for fast and reliable (replicated) access thereby ensuring your users experience with your application is uninterrupted and first class.

When combined with the power of Pivotal Cloud Foundry’s, Pivotal Cloud Cache tile and the new Session State Caching plan, you have a recipe for success!

Feedback

If you have feedback on this release, I encourage you to reach out via StackOverflow, GitHub Issues, or via the comments section. You can also ping me @john_blum on Twitter.

Of course the best feedback comes in the form of contributions.