Keynote: Building a Case for Transformational Change
summary
Argument that combining IaaS and PaaS shifts spending so maintenance falls and innovation rises with a concrete target of reduce maintenance from ~60% to ~25% by decommissioning legacy apps and moving workloads. Claim that PaaS affects revenue with examples like airline kiosk in under four months and caution that config tools like Puppet and Chef are infrastructure automation not true PaaS. Verizon pilot migrates tech tablet to PaaS with Pivotal and scales successfully, containers praised but limited by current enterprise security.
AI-written summary · about
chapters (12)
- 0:00Introduction to transformation
- 1:43Application portfolio value explained
- 4:17IaaS vs PaaS for enterprises
- 7:07PaaS impact on revenue
- 9:58Mobility and PaaS connection
- 11:20Agile development challenges
- 12:22Containers and security concerns
- 13:48Cloud adoption and security
- 14:52Why both IaaS and PaaS matter
- 16:17Scaling applications at Verizon
- 18:01Tech Tablet pilot success
- 19:51Future with IoT and PaaS
related talks
11mKeynote: The Golden Goose: Scaling CD Platforms in the Enterprise Through Self-Service
22mThe Journey to DevOps: What I Learned
13mKeynote: Fireside Chat with Craig McLuckie
18mKeynote: Allstate / CompoZed Labs - One Year Later
23mKeynote: Transformation Success: The C-Suite’s View
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
52mCreating Lasting Change
05mTransforming how the world operates software