Adopting PCF At An Automobile Manufacturer - Gregor Zurowski, Thomas Seibert (Mercedes-Benz)
summary
Mercedes builds a microservice platform on Pivotal Cloud Foundry using Spring Boot, Spring Cloud and Spring Cloud Services, a Netflix Zuul API gateway, Eureka registry and a config server; teams get isolated PCF orgs/spaces and a shared-services space for global components. They deploy separate apps per major version (semver), run three CF foundations (dev/test, integ/pre-prod, prod), roll out 20 countries in under five months with zero critical incidents, shorten integration ramp from ~30 days to 2–3 days, and run multiple daily production deploys via a custom zero-downtime process.
AI-written summary · about
chapters (10)
- 0:00Introduction to PCF adoption
- 1:28Customer journey challenges
- 3:34Mission and platform goals
- 6:44Rollout and scaling achievements
- 8:09Architectural decisions
- 13:55Isolation and decoupling
- 20:26Development topics
- 28:57Lessons learned
- 32:06Organizational changes
- 44:05Q&A session
related talks
14mKeynote: Daimler Hybrid Cloud – Daimler Journey with Cloud Foundry
09mEnterprise-Ready PCF - Making The Cool Super Cool
50mGoing from Nothing to Production Within an Hour
06mLightning Talk: Experiences with CF as the Main Target Platform for our Company
19mConversation with Dr. Andreas Häberli & Marcel Walker
33mCloud Foundry Weekly: Live at CF Day Germany
32mStories of Growth and Competitive Edge with Cloud Foundry
06mAccelerate Rapid Software Innovation with Virtustream Pivotal Cloud Foundry Service
