Building Cloud Foundry Components on the Java Platform
summary
Organization runs Cloud Foundry on vSphere at BYU and now hosts 200 applications after rolling out internally; team builds components in Java and Spring Boot deployed with BOSH. Concrete deliverables include a custom NATS client and an etcd Java client, a tunnel for remote JMX/debug, a loggregator→Splunk adapter that tags events with app metadata, and about a dozen service brokers for Oracle, Splunk, AppDynamics and SSO — all running in production.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:20Disclaimer
- 1:11LDS Cloud Foundry
- 3:18Team
- 6:55Custom Components
- 9:16Service Brokers
- 9:45Why use Java
- 10:06Why not use Java
- 11:14Cloud Foundry Libraries
- 12:52Cloud Foundry Project
- 13:10Cloud Foundry Service Broker
- 18:22Service Broker Source Code
- 19:50Contact Information
related talks
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
33mCase Study: Orange Labs & Cloud Foundry
01h 25mWhat's New in CloudFoundry
48mCloud Foundry - your PaaS on OpenStack
33mCloud Foundry Weekly: Live at CF Day Germany
30mCloud-Native Java with Spring Cloud Services
02mCloud Foundry
23mThe Genesis of Cloud Foundry: Using Open Source Tools to Easily Deploy...
