LATEST VERSION: 8.0.0 - CHANGELOG
Pivotal GemFire® v8.0

Recommended Development Model

Recommended Development Model

The Spring development environment provides several programming models that allow developers to create and configure Java applications that use GemFire caches and regions for high-performance data access. These models include using Spring dependency injection with the standard GemFire cache.xml file to configure GemFire; using the GemFireTemplate (similar to the Spring Data JDBCTemplate); and using the Spring XML Namespace to configure GemFire data access.

Pivotal recommends that developers use the Spring XML Namespace to configure their GemFire components and this chapter provides an overview of that model. For information on other programming models, see the Spring Data GemFire Reference Guide.

Using the Spring XML namespace provides the following advantages:
  • Developers can architect their applications so that data access and business logic are separated from configuration and operation code.
  • Developers can use Spring property management features and Spring Expression Language (SpEL) to configure thier applications.
  • Developers can use Spring Framework features such as transaction management and modular configuration in their applications.
  • The Spring Tool Suite (STS) provides support for creating and editing Spring XML namespaces and Java code, including code completion, pop-up annotations, and validation. You can also use other IDEs.
  • Developers can replace the standard GemFire cache.xml, which provides limited configuration options, with the Spring XML application context configuration. This also eliminates the requirement for callbacks that implement the GemFire Declarable interface, which is not required when using Spring.