Leaving Your Comfort Zone - Garmin & Cloud Foundry
summary
Garmin prototypes a production Cloud Foundry platform in four weeks using Pivotal Cloud Foundry, VMware vSphere, Ops Manager and the Ops Metrics tile, fronted by AAMI, F5 and engine x URL rewrites to avoid code changes. Architecture runs two CF deployments per data center (adding a second AZ next) and aims to migrate SSO first; current monolith pool is ~50 servers with ~50 WARs, a past outage cost ~50 man‑hours and 12 people. App monitoring uses AppDynamics plus a Splunk drain; platform auto‑scales and is staged for production but apps are not yet live.
AI-written summary · about
chapters (8)
- 0:00Introduction and team overview
- 1:05About Garmin and its evolution
- 6:02Why change from legacy infrastructure
- 9:31Cloud Foundry proof of concept journey
- 16:14Cloud Foundry architecture design
- 21:12Monitoring Cloud Foundry environment
- 27:11Application monitoring strategies
- 30:43Production management and future steps