Building a private PaaS
Now that your enterprise has made the decision to go the private PaaS route, where do you start? What should you think about first, and with the many options on the market today, which one should you choose? Here are the seven steps to deploying your own private PaaS:
1. Identify stack proliferation
2. Identify value distribution across different types of apps (i.e., mission-critical, business)
3. Identify stakeholders: developers vs. IT operators
4. Identify the deployment model: private IaaS/virtualization or operating systems on bare metal
5. PaaS vendor selections
a) Identify key value props: trivialize application ops, equip developers/cloud app developers
b) What are the highest value stacks (their proliferation value)?
c) Remaining stacks: lowest-common denominator PaaS
d) Ensure alignment with the runtime vendor (e.g. with MS for .NET)
e) PoC to test key assumptions, product readiness
6. Rollout time: up to eight weeks
7. Let it catch on like wildfire: Evangelize these new cloud platforms to developers so they can forklift existing apps to the PaaS for immediate value
What do enterprises gain with private PaaS?
• Improved project agility
• Improved developer productivity
• Reduced administration overhead
• Improved resource utilization efficiency
• Improved billing transparency
However, I would like to point out that some applications are not meant for PaaS. PaaS tends to be best suited to Web and SOA applications, as well as large composite applications. Traditional client/server workloads typically aren’t compatible with PaaS architectures.
Overall, it was a great panel and I really enjoyed participating with Diane and Guy. I hope this summary was beneficial, and please let me know if you have any questions or feedback. I’d be very interested in hearing your perspective on the PaaS industry and how you see it playing out.
Sinclair Schuller is CEO of Apprenda; previously, he worked for Morgan Stanley, Eden Communications, and the State University of New York.