8. Application Resolution Alternatives
Though we highly recommend using Maven Repository for application resolution and registration
in Cloud Foundry, there might be situations where an alternative approach would make sense. Following alternative options
could come handy for resolving applications when running on Cloud Foundry.
- With the help of Spring Boot, we can serve static content
in Cloud Foundry. A simple Spring Boot application can bundle all the required stream/task applications and by having it
run on Cloud Foundry, the static application can then serve the Über-jar’s. From the Shell, you can, for example, register the
app with the name
http-source.jar via --uri=http://<Route-To-StaticApp>/http-source.jar. - The Über-jar’s can be hosted on any external server that’s reachable via HTTP. They can be resolved from raw GitHub URIs
as well. From the Shell, you can, for example, register the app with the name
http-source.jar via --uri=http://<Raw_GitHub_URI>/http-source.jar. - Static Buildpack support in Cloud Foundry is another
option. A similar HTTP resolution will work on this model, too.
- Volume Services is another great option.
The required Über-jar’s can be hosted in an external file-system and with the help of volume-services, you can, for
example, register the app with the name
http-source.jar via --uri=file://<Path-To-FileSystem>/http-source.jar.