Making the Leap: Transitioning Enterprises to a PaaS Mindset
summary
Argues that Platform as a Service is a disruptive shift and gives specific numbers from 451 research — 42 percent of workloads target cloud, 40 percent are still in virtualization, 6 percent in orchestration — and recommends a progression: start with public PaaS (Pivotal Web Services, AppFog) then move private only when needed. Advises using Cloud Foundry buildpacks, manifests and the cf marketplace, make data accessible to the platform, adopt 12-factor apps, favor greenfield or API projects and provide developer sandboxes.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:03The Goal
- 3:24The Problem
- 6:28Why Cloud Foundry
- 7:55Challenge Response
- 9:30New Hotness
- 9:45Big Approach
- 11:05Cloud Foundry Options
- 11:35Whats the Answer
- 13:02Config Management
- 14:43Integration
- 16:08Policies and constraints
- 19:00What is 12factor
- 21:07Budget
- 23:56Outro
related talks
16mCloud Capabilities Through an Enterprise PaaS
18mSunrise of Platforms as Services (PaaS)
15mPaaS isn’t enough: your internal platform in Multi Cloud
33m“PaaS”, The Secret Weapon of Coders in Cloud Wars
32mBottom Up Enterprise Transformation - Kyle Campos, CSAA Insurance
27mCloud Foundry Compared with Other PaaSes
29mLet's call platforms what they really are, ways to provide something-as-a-Service
25mPlatform Engineering for Private Cloud