On behalf of the Spring and Apache Geode communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.1.1.RELEASE as well as 1.2.0.M2.

Bits for 1.1.1.RELEASE are available in Maven Central.

Bits for the 1.2.0.M2 release are available in the Spring Milestone Repository.

What’s New

SBDG 1.1.1.RELEASE has been upgraded to Spring Boot 2.1.8.RELEASE while SBDG 1.2.0.M2 has been upgraded to Spring Boot 2.2.0.M6.

Additionally, both 1.2.0.M2 and 1.1.1.RELEASE now support running your Spring Boot, Apache Geode ClientCache applications in Pivotal Platform using Pivotal Cloud Cache (PCC) as a specific user.

See Issue-44 for more details.

This is useful if you are deploying Spring Boot applications to Platform using PCC and the app needs read-only access.

In the words of the PCC product director, Pulkit Chandra, "With v1.9.0 we are introducing the concept of "shared service instances", which means an app in Space A can access a Cloud Cache cluster in Space B, but will only be able to "read" the data. This ensures for a healthy pattern of isolation for each domain cluster, where one space has the "read/write" access while others only have "read" access."

This capability and 1.9 are still in development, so this feature is tentatively planned for 1.9. However, in anticipation for this UC in Pivotal Platform, SBDG has you covered.

This feature is not limited to only being used when deploying your Spring Boot apps to Pivotal Platform. SBDG’s support for a specific runtime user works equally well when running your Spring Boot apps off Platform, connected to an externally managed Apache Geode cluster.

See the documentation for more details.

For a complete list of changes in the 1.1.1.RELEASE see the changelog.

For a complete list of changes in the 1.2.0.M2 release, see the changelog.

What’s Next

All efforts are now focused on getting to 1.2.0.M3.

In the next release you will be able to annotate your Spring Boot, Apache Geode or Pivotal Cloud Cache based applications with the new @EnableClusterAware annotation and your app will seamlessly switch between local-only environments and a client/server environment depending on whether a server or cluster of servers can be detected by SBDG.

Preview:

Cluster-Aware, Spring Boot Apache Geode application

@SpringBootApplication
@EnableClusterAware
class MySpringBootApacheGeodeClientCacheApplication { ... }

When a cluster is present in your runtime environment, then the @EnableClusterAware annotation (which is also meta-annotated with SDG’s @EnableClusterConfiguration annotation) will additionally push configuration metadata from your client to the server.

For example, if you have any client Regions defined in your application (very common) that need to have server-side Regions by the same name, then SBDG will handle this for you.

We think this will be a useful feature at development-time when you are potentially switching environments very rapidly, iterating on your application in order to get feedback quickly, such as being able to run tests and debug locally, and then push back to your test/staging environment for higher level acceptance and integration testing.

A preview of this feature can already be found in the documentation for the 1.2.0.BUILD-SNAPSHOT. Give it a try!

1.2.0.M3 is tentatively scheduled for Tuesday, September 24th.

Feedback

As always, your feedback is most welcomed and appreciated.

Issues | PR | StackOverflow