The main theme of this release was to add support for hybrid cloud deployments.
For instance, perhaps you want to push and run your Spring Boot, Apache Geode or Pivotal GemFire applications on Pivotal CloudFoundry (PCF), but connect those applications to an externally managed, standalone Apache Geode or Pivotal GemFire cluster. Now, SBDG allows you to do just that.
Technically, SBDG takes advantage of a feature in PCF called CUPS, or Create User-Provided Service. By defining your own service descriptor you can connect your Spring Boot applications to externally managed services, like databases, message queues and even In-Memory Data Grids & Caches like Apache Geode or Pivotal GemFire.
By following a prescribed service descriptor format, it makes it simple to switch to a platform managed service like Pivotal Cloud Cache when you need it.
Indeed, we believe this is an important stepping stone for users making their way to a Cloud-Native platform, like PCF, where they still have much invested in their legacy architectures.
We do highly recommend using a managed service like Pivotal Cloud Cache for your application and Microservices caching needs, but we also realize that making this switch is not as easy as flipping the switch.
We want to help you get there. After all, Cloud-Native (Data) Patterns are crucial to the modern application architecture, particularly when talking about things like high availability and resiliency as well as making effective use of your computing resources.
In addition to hybrid cloud support, we also added:
Auto-configuration for logging.
Support to target specific Pivotal Cloud Cache (PCC) service instances when multiple instances are bound to your Spring Boot app.
Upgrades to Spring Boot
Upgrade to Spring Test for Apache Geode & Pivotal GemFire (STDG)