Simplify Cloud Applications using Spring Cloud Connectors
summary
Spring Cloud Connectors claims one artifact (jar/war) runs unchanged on Cloud Foundry, Heroku and locally by inspecting env vars (VCAP_SERVICES, DYNO) and auto‑creating beans like DataSource, RabbitMQ and Mongo factories. Demos show a Spring Boot 1.2 app (Gradle build) serving ~2,700 postal‑code records paged 20 at a time, replicated on CF and Heroku, and a front end wired via Feign client to a bound user‑provided service. Extension points are CloudConnector / ServiceInfoCreator / ServiceConnectionCreator and the demos work as shown.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:15Agenda
- 4:30Cloud Apps Awareness: Cloud Foundry Instance Information
- 5:01Cloud Apps Awareness: Cloud Foundry Services
- 5:53Cloud Apps Awareness: Heroku Services
- 6:52Spring Cloud Goals
- 8:17Scanning for services
- 12:20Taking over control: Working with specific services
- 13:11Taking over control: Configuring Services
- 15:21Acquiring generic services
- 18:16Deploy to Cloud Foundry
- 33:31Taking over control: Specifying services
- 35:32Services Supported
- 39:51Explicit Cloud Config
- 42:18Cloud Config with Scanning
- 42:40Consuming Service Beans: Explicit Config
- 44:30Axes of Extensibility
- 46:35Extensibility Overview
- 48:05Cloud Platform Extensibility
- 50:06Registering Cloud Connector
- 53:38Registering Service Info Creators
- 55:03Cloud Service Extensibility
- 59:28Framework extensibility registration
related talks
30mCloud-Native Java with Spring Cloud Services
01h 29mThinking Outside the Container: Running Standalone Apps on Cloud Foundry
30mA Guided Tour From Code Base to Platform - Aaron Spiegel, Paul C. Warren, Maggie Ambrose
01h 31m12 Factor, or Cloud Native Apps for Spring Developers
39mMaking Production as Smooth as Development with Azure Spring Apps
33mCloud Foundry Weekly: Live at CF Day Germany
26mMulti-Cloud Native Data with Spring and VMware Data Solutions
09mRunning Java and Spring on Azure with Cloud Foundry