Using Stackato to make your own PaaS on vSphere
by Troy Topnik

Troy Topnik, September 26, 2011
Whitepaper - vSphere Private PaaS

We've written a fair bit about what Stackato is and how it works, but we haven't blogged much about why you would want to consider it. That's because there are different reasons, depending on who you are.

We've prepared a whitepaper which answers the "why" question for IT managers who have already made an investment in vSphere infrastructure or are planning on doing so: Extending your VMware Cloud Infrastructure with a Private Platform-as-a-Service.

Agility with Control

Modern web development frameworks are meant to be agile. An ecosystem of deployment tools and hosting providers have grown up to support these frameworks and web developers have been using them to get their applications up and running very quickly. This framework hosting is what we refer to as Platform as a Service (Paas).

Though it's incredibly convenient for developers to not have to worry about application hosting, it's not an option in some companies. Many companies have already made a significant investment on hardware and virtualization software, and would like to realize the full benefit of that investment. Many have concerns about hosting their applications with third parties.

This paper presents the business case for a private PaaS: using Stackato to provide a flexible application hosting environment on vSphere clusters and other virtualized infrastructure.

Who is this for?

Web developers already know about the benefits of managed application hosting. This paper is for sysadmins, IT teams, system integrators and the people they report to. If you're one of those people, have a look and let us know what you think.

Subscribe to ActiveState Blogs by Email

Share this post:

Category: stackato
About the Author: RSS

As ActiveState's Technical Product Manager for Stackato, Troy Topnik is responsible for defining and prioritizing the product roadmap to build the best cloud platform for deploying applications. Since joining ActiveState in 2001, he has held roles in Technical Support, Training, and Technical Writing. He believes in documentation-driven development as a pragmatic path to a better user experience.