Making the LeapTransitioning Enterprises to a PaaS Mindset
Richard Seroter | @rseroter | CenturyLink
I.T. concerns
server sprawlconfiguration drift
rising costs
pace of tech
inconsistent
architecture
stale skillsets
slow innovation
untested failure
cases
compliance
shifting budgets
aversion to change
Why use
Cloud Foundry?
1) Faster delivery cycles
2) Quick experiments
3) Low barrier to entry
4) App-centric
Challenge There are major cultural obstacles to overcome
Response It *does* require changes, and teamwork
Challenge What am I supposed to do with legacy apps?
Response Extend apps and try to share data
Challenge Where am I supposed to put this thing?
Response May be a progression, but keep data close
Challenge This changes how we do config management!
Response The focus switches from the hardware to the app
Challenge These environments won’t integrate with others
Response Look to marketplace to aid transition
Challenge PaaS gives developers too much freedom!
Response PaaS introduces policies and constraints
Challenge PaaS restricts developer freedom!
Response Developers work in a rich functional sandbox
Challenge You’re making me change how my apps look.
Response 12 factor apps are more flexible, cloud or not
Challenge I don’t know what apps to put in a PaaS!
Response Greenfield apps, API gateway, mobile, blogs