The early cloud computing adopters, mostly website developers, made initial use of emerging public PaaS technology such as Heroku, Engine Yard, and Google App Engine. Driving this movement was the use of the instant sandbox, which allowed developers to begin writing their apps without worrying about the underlying infrastructure.
However, enterprises practically ignored public PaaS for obvious reasons, such as security and governance. While enterprises have the desire to create a standard development and deployment platform for the enterprise, they cannot afford the risks of multitenant public cloud services.
So how do you make PaaS work for your enterprise? The answer lies in understanding new models of delivery, such as private PaaS. Moreover, there are emerging patterns of use that provide more business agility. These include standardized business solutions development, such as a common business system, or a cost-effective platform to build and externalize services to customers and partners, such as providing and managing web services that allow controlled access to core business data or processes from outside the organization — in essence, turning the enterprise into a cloud provider.
The successes of this technology are beginning to appear, as is the business case for leveraging private PaaS. Traditional approaches to application development and testing are still very expensive. IT wants to get out of the cycle of endless hardware and tool upgrades. We need to centralize and standardize development around a common toolset and platform that will support how applications are built for years to come.
In addition, PaaS provides the ability to improve development operations (devops). It allows users to more tightly couple the needs of the business with the ability to define and build business applications. The path to PaaS, specifically private PaaS, is not obvious. An enterprise needs a good understanding of its requirements, including data, applications, services, processes, the needs of the users, and the ultimate needs of the business.
In this paper, we’ll help you understand the path to a more effective and efficient way to design, build, test, and deploy business applications. Using case studies of JPMorgan Chase, Diebold, and AmerisourceBergen, we’ll also help you understand the core drivers, the emerging patterns, and how you should consider PaaS within your enterprise IT strategy.
If you follow the advice in this paper, chances are you’ll be successful with your PaaS deployment. Miss any of the steps or ignore the advice and you’re putting your project at risk.
- What today’s enterprise needs in business applications
- The rise of private PaaS
- Understanding the PaaS market
- Leveraging private PaaS at JPMorgan Chase
- The value of private PaaS
- Evaluating PaaS technology: a how-to guide
- Step one: public or private?
- Step two: creating a cloud-based application or service
- Step three: service delivery and management capabilities
- Step four: what to do when things go wrong
- Call to action
- About David S. Linthicum
- About GigaOM Research