Platform as a service

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Platform as a service (PaaS) is a category of cloud computing services that provides a platform allowing customers to develop, run and manage Web applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app.[1][2][3] PaaS can be delivered in two ways: as a public cloud service from a provider, where the consumer controls software deployment and configuration settings, and the provider provides the networks, servers, storage and other services to host the consumer's application; or as software installed in private data centers or public infrastructure as a service and managed by internal IT departments.[4][5]

Development and uses[edit]

Fotango, a London (Old Street) based company owned by Canon Europe launched the world's first public platform as a service known as 'Zimki'. Developed in 2005 with a beta launch in March 2006 and a public launch at EuroOSCON in 2006.[6] Zimki was an end to end JavaScript web application development and utility computing platform that removed all the repetitive tasks encountered when creating web applications and web services. All aspects of infrastructure and operations from setting up servers, scaling, configuration, security and backups were done automatically by Zimki, enabling developers to get on with doing what they enjoy: writing code. Zimki introduced the tagline 'Pre-Shaved Yaks' [7] to describe the removal of all these repetitive tasks that got in the way of coding.[8]

Zimki was a pure play 'pay as you go' platform which enabled developers to build and deploy applications without incurring any start-up costs on a true utility based computing platform. Charging was done on storage used, network traffic and JSOPs (Javascript Operations). It provided a multi-tenant platform where developers created entire applications (front and back end through SSJS) using a single language - Javascript, with all development and application control exposed through APIs and a range of component services from a NoSQL object store to Message Queue services.[9] Furthermore, all functions within Zimki could be exposed as web services and Zimki provided billing analysis down to individual functions.

Whilst the Zimki platform was rapidly growing and Fotango was profitable, the parent company decided this area was not core [10] and the service was closed in Dec 2007.[11] At the time of its closure, Zimki had several thousand developer accounts and had demonstrated the technical viability of Platform as a Service but also provided the first example of the perils of being dependent upon a single provider.[12] This risk had been highlighted in July 2007, when the CEO gave a presentation on Zimki at OSCON 2007 which announced that Zimki would no longer be open sourced and discussed the future of what was then called Framework as a Service (later renamed to Platform as A Service) covering the importance of a market of providers based upon an open source reference model [13]

In April 2008, Google launched App Engine, with a free trial version limited to 10,000 developers.[14] This was said to have "turned the Internet cloud computing space into a fully-fledged industry virtually overnight."[15]

The original intent of PaaS was to simplify the code-writing process for developers, with the infrastructure and operations handled by the PaaS provider. Originally, all PaaSes were in the public cloud. Because many companies did not want to have everything in the public cloud, private and hybrid PaaS options (managed by internal IT departments) were created.[16]

PaaS provides an environment for developers and companies to create, host and deploy applications, saving developers from the complexities of the infrastructure side (setting up, configuring and managing elements such as servers and databases). PaaS can improve the speed of developing an app, and allow the consumer to focus on the application itself. With PaaS, the consumer manages applications and data, while the provider (in public PaaS) or IT department (in private PaaS) manages runtime, middleware, operating system, virtualization, servers, storage and networking.[4][17] Development tools provided by the vendor are customized according to the needs of the user.[18] The user can choose to maintain the software, or have the vendor maintain it.[4]

PaaS offerings may also include facilities for application design, application development, testing and deployment, as well as services such as team collaboration, web service integration, and marshalling, database integration, security, scalability, storage, persistence, state management, application versioning, application instrumentation, and developer community facilitation. Besides the service engineering aspects, PaaS offerings include mechanisms for service management, such as monitoring, workflow management, discovery and reservation.[19][20]

Market[edit]

According to research report by MarketsandMarkets, the PaaS market is expected to reach $6.94 Billion by 2018, at a compound annual growth rate (CAGR) of 32.54%. The major forces driving the PaaS market are the key factors in application development process such as agility, scalability, limited need for expertise, easy deployment, and reduced cost and development time. In terms of geographies, North America continues to be the biggest market for PaaS solutions.[21]

Advantages and disadvantages[edit]

The advantages to PaaS are primarily that it allows for higher-level programming with dramatically reduced complexity; the overall development of the application can be more effective, as it has built-in infrastructure; and maintenance and enhancement of the application is easier.[3] It can also be useful in situations where multiple developers are working on a single project involving parties who are not located nearby.[2]

The primary disadvantage would be the possibility of being locked in to a certain platform. However, most PaaSes are relatively lock-in free.[15]

Types[edit]

Public, private and hybrid[edit]

There are several types of PaaS, including public, private and hybrid.[16] PaaS was originally intended as an application solution in the public cloud, before expanding to include private and hybrid options.[16]

Public PaaS is derived from software as a service (SaaS),[14] and is situated in cloud computing between SaaS and infrastructure as a service (IaaS).[1] SaaS is software that is hosted in the cloud, so that it doesn't take up hard drive or server space. IaaS provides virtual storage from a provider with adjustable scalability.[1] With IaaS, the user still has to manage the server, whereas with PaaS the server management is done by the provider.[22]

A private PaaS can typically be downloaded and installed either on a company's on-premises infrastructure, or in a public cloud. Once the software is installed on one or more machines, the private PaaS arranges the application and database components into a single hosting platform.[23] Private PaaS vendors include Apprenda, which started out on the Microsoft .NET platform before rolling out a Java PaaS; Red Hat's OpenShift and Pivotal Cloud Foundry.[24] Apprenda and Microsoft are considered to be two of the only PaaSes that provide superior .NET support.[16]

Mobile PaaS[edit]

Initiated in 2012, mobile PaaS (mPaaS) provides development capabilities for mobile app designers and developers.[25] The Yankee Group identified mPaas as one of its themes for 2014, naming a number of providers including Kinvey, CloudMine, AnyPresence, FeedHenry, FatFractal and Point.io.[26][27]

Open PaaS[edit]

Open PaaS does not include hosting, but rather it provides open source software allowing a PaaS provider to run applications in an open source environment. For example, AppScale allows a user to deploy some applications written for Google App Engine to their own servers, providing datastore access from a standard SQL or NoSQL database. Some open platforms let the developer use any programming language, database, operating system or server to deploy their applications.[28][29]

PaaS for Rapid Development[edit]

In 2014, Forrester Research defined Enterprise Public Cloud Platforms for Rapid Developers as an emerging trend, naming a number of provides including OutSystems, Mendix, Salesforce.com, and Acquia.[30]

System types[edit]

PaaS is found on the following types of systems:

Add-on development facilities
These facilities customization of existing SaaS applications, often requiring PaaS developers and their users to purchase subscriptions to the add-on SaaS application.[31]
Stand alone environments
Stand-alone PaaS environments do not include technical, licensing or financial dependencies on specific SaaS applications or web services, and are intended to provide a generalized development environment.[31]
Application delivery-only environments
Delivery-only PaaS offerings generally focus on hosting services, such as security and on-demand scalability. The service does not include development, debugging and test capabilities, though they may be supplied offline (via an Eclipse plugin, for example).[31]

Providers[edit]

There are various types of PaaS providers. All offer application hosting and a deployment environment, along with various integrated services. Services offer varying levels of scalability and maintenance.[15] Developers can write an application and upload it to a PaaS that supports their software language of choice, and the application runs on that PaaS.[32]

Public PaaS providers and private PaaS vendors include:

See also[edit]

References[edit]

  1. ^ a b c Brandon Butler, “PaaS Primer: What is platform as a service and why does it matter?” Network World, February 11, 2013.
  2. ^ a b “Understanding the Cloud Computing Stack: SaaS, PaaS, IaaS,” Rackspace, October 22, 2013.
  3. ^ a b William Y. Chang, Hosame Abu-Amara, Jessica Feng Sanford, Transforming Enterprise Cloud Services, London: Springer, 2010, pp. 55-56.
  4. ^ a b c Judith Hurwitz, Marcia Kaufman, Fern Halper and Dan Kirsh, “What Is Platform as a Service (PaaS) in Cloud Computing?” Hybrid Cloud For Dummies, Hoboken, NJ: John Wiley & Sons, 2012.
  5. ^ "The NIST Definition of Cloud Computing" (PDF). National Institute of Science and Technology. Retrieved 24 July 2011. 
  6. ^ Zimki, hosted JavaScript environment, http://radar.oreilly.com/2006/09/zimki-hosted-javascript-enviro.html
  7. ^ What is a pre-shaved Yak, https://www.flickr.com/photos/zimki/243779431/in/photostream/
  8. ^ Pre Shaved Yaks, http://archive.ianwinter.co.uk/2007/09/25/zimki-is-no-more/
  9. ^ Fotango Opens its Zimki Customer API, http://www.prnewswire.co.uk/news-releases/fotango-opens-its-zimki-customer-api-153777895.html
  10. ^ A personal journey, http://blog.gardeviance.org/2009/04/there-and-back-again-personal-journey.html
  11. ^ Zimki Shuts Down, http://blog.gerv.net/2007/09/zimki_shuts_down/
  12. ^ Zimki closure shows the perils of hosted web platforms, http://www.itwriting.com/blog/337-zimki-closure-shows-the-perils-of-hosted-web-platforms.html
  13. ^ OSCON Keynote 2007, http://mais.uol.com.br/view/v1xaxe2lamb3/oscon--commoditisation-of-it-and-what-the-future-holds-0402D4B10386?types=A
  14. ^ a b Jack Schofield, “Google angles for business users with ‘platform as a service’,” The Guardian, April 16, 2008.
  15. ^ a b c Dion Hinchcliffe, “Comparing Amazon’s and Google’s Platform-as-a-Service (PaaS) Offerings,” ZDNet, April 11, 2008.
  16. ^ a b c d Mike Kavis, “Top 8 Reasons Why Enterprises Are Passing On PaaS,” Forbes, September 15, 2014.
  17. ^ Sean Ludwig, “An ugly duckling no more: Why Platform-as-a-Service is poised for huge growth,” VentureBeat, October 8, 2012.
  18. ^ Andrea Peiro, “Keep Your Head in the Cloud,” Inc., January 2009.
  19. ^ M. Boniface, “Platform-as-a-Service Architecture for Real-Time Quality of Service Management in Clouds,” ieee.org, May 2010.
  20. ^ Chen, Tse-Shih, et al. "Platform-as-a-Service Architecture for Parallel Video Analysis in Clouds." Advances in Intelligent Systems and Applications-Volume 2. Springer Berlin Heidelberg, 2013. 619-626.
  21. ^ "Platform as a Service (PaaS) Market", Markets and Markets, February 2013.
  22. ^ Andrew C. Oliver, “Which freaking PaaS should I use?” InfoWorld, October 8, 2012.
  23. ^ Jason Brooks, “Apprenda 3.0 Brings Private PaaS to .NET Developers,” eWeek, January 6, 2012.
  24. ^ Ben Kepes, “Apprenda Extends Its PaaS And Aims A Kick In The Direction of Red Hat,” Forbes, October 6, 2014.
  25. ^ Anthony Wing Kosner, “Developers in Demand: Platform As A Service Is Key to Growth of Mobile Cloud Computing,” Forbes, June 8, 2012.
  26. ^ Yankee 2014 Predictions Mobility hits a tipping point, Yankee Group, 2014.
  27. ^ Christina Warren, “How to Pick a Server for Your App,” Mashable, November 16, 2011.
  28. ^ “Interview With Brian Sullivan – Open Platform As A Service,” openplatformasaservice.com, 2010.
  29. ^ “The Top 20 Platform as a Service (PaaS) Vendors,” clouds360.com. Accessed January 23, 2015.
  30. ^ "Forrester Wave: Enterprise Public Cloud Platforms," Q4 2014.
  31. ^ a b c “Platform as a Service (PaaS),” Quality Testing, December 22, 2010.
  32. ^ Nancy Gohring, “Platform as a service heats up,” Computerworld, July 8, 2013.