On behalf of the team and the community, I am pleased to announce the release of Spring Boot for Apache Geode and Pivotal GemFire 1.0.0.M2.

In summary this release brings the following improvements:

• Auto-configuration support for Spring Session when using Apache Geode, Pivotal GemFire or Pivotal Cloud Cache (PCC) to manage and store your Spring Boot application’s (HTTP) Session state.

• Recognition of spring.cache.type when using Spring’s Cache Abstraction auto-configured with Spring Boot.

• Additions and improvements to the documentation.

• Upgrades to Spring Framework 5.0.8.RELEASE, Spring Boot 2.0.4.RELEASE and Spring Data Kay-SR9

This release builds on the recently minted Spring Session for Apache Geode/Pivotal GemFire (SSDG) 2.0.5.RELEASE.

1 of the key additions to SSDG was to enable dynamic configuration of Spring Session with Apache Geode/Pivotal GemFire/PCC using Properties along with a new SpringSessionGemFireConfigurer callback interface. That way, even in the context of Spring Boot’s auto-configuration, users have the ability to customize the configuration to meet their application requirements.

Configuration with Properties

In addition to the Properties discussed here and documented here, Spring Boot for Apache Geode & Pivotal GemFire additionally recognizes the following properties:

• spring.session.timeout

• server.servlet.session.timeout

Still, spring.session.data.gemfire.session.expiration.max-inactive-interval-seconds takes precedence over spring.session.timeout, which takes precedence over server.servlet.session.timeout if any combination of these properties are set.

Spring Boot for Apache Geode/Pivotal GemFire additionally recognizes and respects spring.session.store-type. However, and unfortunately, this property cannot be set to either gemfire or geode as these values are not recognized as a valid (enumerated) values by Spring Boot itself.

Configuration using a Configurer

Spring Boot for Apache Geode & Pivotal GemFire adds nothing beyond what is already provided by Spring Session for Apache Geode/Pivotal GemFire with respect to the new SpringSessionGemFireConfigurer call back interface, as discussed here and documented here.

What’s Next

Next up, Spring Boot for Apache Geode & Pivotal GemFire will provide OOTB HealthIndicators to assess and monitor the runtime health of your Apache Geode/Pivotal GemFire powered Spring Boot applications.

More information about Spring Boot HealthIndicators can be found here.

This will be available in next release, 1.0.0.M3.

Even longer term, we are planning to add support for Spring Boot Actuator. There is an effort underway to retrofit Apache Geode/Pivotal GemFire’s Stats architecture with Micrometer. This will serve as the basis for Spring Boot for Apache Geode & Pviotal GemFire’s Actuator support. This will most likely be available in SBDG 1.1.

Feedback

Try it out!

You can get the new Spring Boot for Apache Geode or Pivotal GemFire bits from Spring’s libs-milestone Repository and begin building Apache Geode/Pivotal GemFire powered Spring Boot applications by including the following dependency:

• org.springframework.geode:spring-geode-starter (Apache Geode)

• org.springframework.geode:spring-gemfire-starter (Pivotal GemFire/PCC)

Any feedback and/or contributions are always welcomed and appreciated: Issues | PR | StackOverflow.

Also be sure to checkout SpringOne Platform this year. There is a lot of great content and speakers. Plus, Luke Shannon and I will be presenting on "Scaling Spring Boot Application in Real-Time", where we will be showcasing this project and much more.