Spring Boot for Apache Geode & Pivotal GemFire automatically applies auto-configuration to several key
application concerns (Use Cases) including, but not limited to:
-
Look-Aside Caching, using either Apache Geode or Pivotal GemFire as a caching provider in
Spring’s Cache Abstraction.
-
System of Record (SOR), persisting application state reliably in Apache Geode
or Pivotal GemFire using Spring Data Repositories.
-
Transactions, managing application state consistently with Spring Transaction Management
and SDG
support for both Local Cache
and Global JTA Transactions.
-
Distributed Computations, run with Apache Geode/Pivotal GemFire’s Function Executions framework
and conveniently implemented and executed with SDG POJO-based, annotation support for Functions.
-
Continuous Queries, expressing interests in a stream of events, where applications are able to react to and process changes to data in near real-time
using Apache Geode/Pivotal GemFire Continuous Query (CQ).
Handlers are defined as simple Message-Driven POJOs (MDP) using Spring’s Message Listener Container,
which has been extended by SDG with its
configurable CQ support.
-
Data Serialization with Apache Geode/Pivotal GemFire PDX,
including first-class configuration
and support in SDG.
-
Security, including Authentication
& Authorization as well as Transport Layer Security (TLS)
using Apache Geode/Pivotal GemFire’s Secure Socket Layer (SSL).
Once again, SDG includes first-class support for configuring Auth
and SSL.
-
HTTP Session state management, by including Spring Session for Apache Geode/Pivotal GemFire on your application’s
classpath.
While Spring Data for Apache Geode & Pivotal GemFire offers a simple, convenient and declarative approach to configure
all these powerful Apache Geode/Pivotal GemFire features, Spring Boot for Apache Geode & Pivotal Gemfire makes it even
easier to do as we will explore throughout this Reference Documentation.