close

Spring Boot for Apache Geode & Pivotal GemFire 1.3.0.M2 Available

On behalf of the Spring, Apache Geode & Pivotal GemFire communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.3.0.M2.

The 1.3.0.M2 release aligns with:

  • Spring Framework 5.2.3.RELEASE

  • Spring Boot 2.3.0.M2

  • Spring Data for Apache Geode & Pivotal GemFire (SDG) 2.3.0.M3

  • Spring Data Neumann-M3

  • Spring Session for Apache Geode & Pivotal GemFire (SSDG) 2.3.0.M2

  • Spring Session Dragonfruit-M2

  • Spring Test for Apache Geode & Pivotal GemFire (STDG) 0.0.13.RELEASE

See the changelog for more details.

This release is available in the Spring Milestone Repository as well as available on Spring Initializer at start.spring.io.

What’s New

SBDG 1.3.0.M2 adds new starters to enable logging in either Apache Geode (org.springframework.geode:spring-geode-starter-logging:1.3.0.M2) or Pivotal GemFire (org.springframework.geode:spring-gemfire-starter-logging:1.3.0.M2).

Out-of-the-box, SBDG imports the org.springframework.boot:spring-boot-starter-logging dependency and uses Logback as the default logging system provider. It also automatically bridges the Log4j API, used by Apache Geode/Pivotal GemFire to log statements in GemFire/Geode components, to SLF4J. Finally, a default, configurable logback.xml file is provided by SBDG to output Apache Geode or Pivotal GemFire log statements at INFO.

You can read the reference documentation for more details.

What’s Next

We have plans to provide an option to preheat the GemFire/Geode oven. In a nutshell, we mean to preload data into a configured GemFire/Geode Region on startup in much the same way as a data.sql file can be provided and picked up by Spring Boot to automatically preload an existing RDBMS table or tables. See Issue #67 for more details and follow our progress.

Also, in addition to adding to the Samples, we plan to make each sample individually buildable and runnable without having to build the entire SBDG project. See Issue #75 for more details and follow our progress.

Feedback

As always, any feedback is greatly appreciated and welcomed.

comments powered by Disqus