Spring/spring-boot-data-geode
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Refer to the Pivotal GemFire Documentation on acquiring Pivotal GemFire or Pivotal Cloud Cache bits from the commercial Pivotal Maven Repository.

Browse Source 
Resolves gh-59.
This commit is contained in:
John Blum
2019-09-27 16:56:06 -07:00
parent 7301dd91cf
commit c2f78ef4aa
1 changed files with 20 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
spring-geode-docs/src/docs/asciidoc/appendix.adoc
View File

@@ -79,9 +79,9 @@ The current set of _auto-configuration_ classes in Spring Boot for Apache Geode
[[geode-gemfire-switch]]
=== Switch from Apache Geode to Pivotal Cloud Cache (a.k.a. Pivotal GemFire)
First, understand that {pivotal-gemfire-website}[Pivotal GemFire] is being replaced by
{pivotal-cloudcache-website}[Pivotal Cloud Cache] (PCC). Therefore, all references to "`gemfire`" also implies for
Pivotal Cloud Cache as well.
First, understand that {pivotal-gemfire-website}[Pivotal GemFire] is being succeeded by
{pivotal-cloudcache-website}[Pivotal Cloud Cache] (PCC). Therefore, all references to Pivotal GemFire (i.e. "`gemfire`")
also implies for Pivotal Cloud Cache (i.e. "`cloudcache`") as well.
When it comes to Spring's support, whether you are developing with Open Source Software (OSS)
{apache-geode-website}[Apache Geode] or developing for {pivotal-cloudcache-website}[Pivotal Cloud Cache],
@@ -90,12 +90,14 @@ Spring has you covered.
At a strategic-level, this means:
1. From Open Source Software (e.g. Apache Geode) to Commercial (e.g. Pivotal Cloud Cache)
2. From Non-Managed (e.g. Standalone) to Managed Environments (e.g. Pivotal CloudFoundry)
2. From Non-Managed Environments (e.g. Standalone, Externally Managed) to Managed Environments (e.g. Pivotal Platform)
3. With little to no code or configuration changes necessary. It just works!
You may also go back and migrate your Spring Boot applications away from Pivotal CloudFoundry when using the commercial
software offering Pivotal Cloud Cache and switch back to Open Source, Apache Geode running in a standalone environment.
SBDG will not (ever) lock you in. It is your choice.
You may also go back and migrate your Spring Boot applications away from Pivotal Platform when using the commercial
software offering, Pivotal Cloud Cache, and switch back to Open Source Apache Geode running in a standalone, externally
managed environment.
SBDG will not (ever) lock you in! It is your choice!
Technically, this means to go from Apache Geode to Pivotal Cloud Cache, you only need to change the SBDG dependency
from:
@@ -164,10 +166,15 @@ dependencies {
}
----
To go back, simple change `spring-gemfire-starter` (or `spring-cloudcache-starter`) back to `spring-geode-starter`.
TIP: To acquire the Pivotal Cloud Cache or Pivotal GemFire bits to use in your Spring Boot applications in place of
Apache Geode, follow these instructions provided in the Pivotal GemFire
https://gemfire.docs.pivotal.io/{pivotal-gemfire-version}/gemfire/getting_started/installation/obtain_gemfire_maven.html[documentation].
To go back, simple change `spring-cloudcache-starter` (or `spring-gemfire-starter`) back to `spring-geode-starter`.
Done!
It should just work without any code or configuration changes and if that is not the case, for whatever reason, then we
It should just work without any code or configuration changes and if this is not the case, for whatever reason, then we
will work to correct it, short of any feature differences between Pivotal Cloud Cache that cannot be accomplished with
Apache Geode by itself.
@@ -177,9 +184,10 @@ environment so that we can provide users with a consistent and reliable experien
that arise by switching environments. Switching environments is especially common as you migrate your Spring Boot
applications from DEV to TEST, into STAGING, and finally, to PRODUCTION.
Of course, it will nearly always be easier to "run" Apache Geode as a "managed" service inside Pivotal CloudFoundry
using Pivotal Cloud Cache, especially if your Use Case requires maximum performance and high availability. We highly
recommend this approach when and where possible.
Of course, it will nearly always be easier to "run" Apache Geode as a "managed" service inside Pivotal Platform
using Pivotal Cloud Cache, especially if your Use Case requires maximum performance and high availability then it will
to manage an externally run Apache Geode cluster. We highly recommend this approach when and where possible, but it is
still your choice.
[[geode-cluster-configuration-bootstrapping]]
=== Running an Apache Geode or Pivotal GemFire cluster using Spring Boot from your IDE