Not logged in Talk Contributions Create account Log in

Article Talk Read Edit View history Search Wikipedia

Platform as a service
From Wikipedia, the free encyclopedia

Main page Platform as a service (PaaS) or application platform as a service (aPaaS) or platform-based service is a category of cloud computing services that allows customers to
Contents provision, instantiate, run, and manage a modular bundle comprising a computing platform and one or more applications, without the complexity of building and maintaining the
Current events
infrastructure typically associated with developing and launching the application(s); and to allow developers to create, develop, and package such software bundles.[1][2]
Random article
About Wikipedia Contents [hide]
Contact us
1 Development and uses
Donate
2 Advantages and disadvantages
Contribute 3 Types
Help 3.1 Public, private and hybrid
Learn to edit 3.2 Communications platform as a service
Community portal 3.3 Mobile platform as a service
Recent changes
3.4 Open PaaS
Upload file
4 Providers
Tools 5 See also
What links here 6 References
Related changes
Special pages
Permanent link Development and uses [ edit ]
Page information
Cite this page
PaaS can be delivered in three ways:
Wikidata item As a public cloud service from a provider, where the consumer controls software deployment with minimal configuration options, and the provider provides the networks,
servers, storage, operating system (OS), middleware (e.g. Java runtime, .NET runtime, integration, etc.), database and other services to host the consumer's application.
Print/export
As a private service (software or appliance) behind a firewall.
Download as PDF
Printable version As software deployed on public infrastructure as a service.[3][4]

The first[5] public platform as a service was Zimki, launched by Fotango, a London-based company owned by Canon Europe. It was developed in 2005, had a beta launch in
Languages
March 2006 and a public launch at EuroOSCON in 2006.[6] Zimki was an end-to-end JavaScript platform for web application development and utility computing that removed
‫اﻟﻌﺮﺑﻴﺔ‬
the repetitive tasks of creating web applications and web services. Zimki automated all aspects of infrastructure and operations, from provisioning and setting up virtual servers,
Deutsch
Español scaling, configuration, security and backups. Zimki introduced the tagline "Pre-Shaved Yaks"[7] to describe the removal of all these repetitive tasks.[8]
Français Zimki was a pure "pay as you go" code execution platform that allowed developers to build and deploy applications or web services without start-up costs, on a true utility-
Bahasa Indonesia
based computing platform. Charging was based on used storage, network traffic and JSOPs (Javascript operations). It was multitenant platform where developers could create
⽇本語
applications (front and back end through SSJS[9]) by using a single language - Javascript. All development, billing, monitoring and application control were exposed through
Português
Русский APIs.[10] There were a range of component services such as No-SQL object store and Message Queue services.[11] All functions in Zimki could be exposed as web services,
中文 and Zimki provided billing analysis down to individual functions.

16 more While Zimki was rapidly growing and Fotango was profitable, the parent company decided that this area was not its core[12] and closed the service in December 2007.[13] At the
time of its closure, Zimki had several thousand developer accounts. It had demonstrated the technical viability of Platform as a Service, but also provided the first example of
Edit links
the perils of being dependent on a single provider.[14] This was highlighted when the CEO (Simon Wardley, known for Wardley maps) announced at OSCON 2007 that Zimki
would no longer be open-sourced and discussed the future of what was then called framework-as-a-service (later called platform-as-a-service) covering the importance of a
market of providers based on an open-source reference model. [15]

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

The original intent of PaaS was to simplify the writing of code, 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.[18]

PaaS provides an environment for developers and companies to create, host and deploy applications, saving developers from the complexities of infrastructure (setting up,
configuring and managing elements such as servers and databases). PaaS can improve the speed of developing an app, and allow its user to focus on the application itself.
With PaaS, the customer 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.[3][19] Development tools provided by the vendor are customized according to the needs of the user.[20] The user can
choose to maintain the software, or have the vendor maintain it.[3]

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.[21][22]

Advantages and disadvantages [ edit ]

The advantages of 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/self up-and-down ramping infrastructure resources; and maintenance and enhancement of the application is thus easier.

Disadvantages of various PaaS providers as cited by their users include increased pricing at larger scales,[23] lack of operational features,[24] reduced control,[24] and the
difficulties of traffic routing systems.[25]

Types [ edit ]

Public, private and hybrid [ edit ]

There are several types of PaaS, including public, private and hybrid.[18] PaaS was originally intended for applications on public cloud services, before expanding to include
private and hybrid options.[18]

Public PaaS is derived from software as a service (SaaS),[16] and is situated in cloud computing between SaaS and infrastructure as a service (IaaS).[1] SaaS is software
hosted in the cloud so that it does not take up hard drive space on the computers of users. IaaS provides virtual hardware 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.[26]

A private PaaS can typically be downloaded and installed either in a company's on-premises data center, 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.[27]

Hybrid PaaS is typically a deployment consisting of a mix of public and private deployments.

Communications platform as a service [ edit ]

A communications platform as a service (CPaaS) is a cloud-based platform that enables developers to add real-time communications features (voice, video, and messaging) in
their own applications without building back-end infrastructure and interfaces.[citation needed] Also, CPaaS and hardware and software specifications are specifically designed to
support (tele)communications applications. These applications and their usage are much more sensitive to jitter, latency and packet losses. Hosted PABX, cellular networks,
(near real-time) applications typically are deployed on CPaaS platforms.

Mobile platform as a service [ edit ]

Initiated in 2012, mobile PaaS (mPaaS) provides development capabilities for mobile app designers and developers.[28] The Yankee Group identified mPaaS as one of its
themes for 2014.[29][30]

Open PaaS [ edit ]

Open PaaS does not include hosting but provides open-source software allowing a PaaS provider to run applications in an open-source environment, such as Google App
Engine. Some open platforms let the developer use any programming language, database, operating system or server to deploy their applications.[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.[17] 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]

See also [ edit ]

Infrastructure as a service
Mobile Backend as a service
Network as a service
Serverless computing
Software as a service

References [ edit ]

1. ^ a b c Brandon Butler (February 11, 2013). "PaaS Primer: What is platform as a service 17. ^ a b Dion Hinchcliffe, "Comparing Amazon’s and Google’s Platform-as-a-Service (PaaS)
and why does it matter?" " . Network World]. Offerings," ZDNet, April 11, 2008.
2. ^ William Y. Chang, Hosame Abu-Amara, Jessica Feng Sanford (15 November 2010). 18. ^ a b c Mike Kavis, "Top 8 Reasons Why Enterprises Are Passing On PaaS," Forbes,
Transforming Enterprise Cloud Services . London: Springer, 2010. p. 55-56. September 15, 2014.
ISBN 9789048198467. 19. ^ Sean Ludwig, "An ugly duckling no more: Why Platform-as-a-Service is poised for
3. ^ a b c Judith Hurwitz, Marcia Kaufman, Fern Halper and Dan Kirsh, "What Is Platform as huge growth," VentureBeat, October 8, 2012.
a Service (PaaS) in Cloud Computing?" Hybrid Cloud For Dummies, Hoboken, NJ: 20. ^ Peiro, Andrea (January 2009). "Keep Your Head in the Cloud" . Inc.
John Wiley & Sons, 2012. 21. ^ M. Boniface, "Platform-as-a-Service Architecture for Real-Time Quality of Service
4. ^ "The NIST Definition of Cloud Computing" (PDF). National Institute of Science and Management in Clouds," ieee.org, May 2010.
Technology. Retrieved 24 July 2011. 22. ^ Chen, Tse-Shih, et al. "Platform-as-a-Service Architecture for Parallel Video Analysis in
5. ^ Wardley, Simon (20 Feb 2015). "On open source, gameplay and cloud" . Bits or Clouds." Advances in Intelligent Systems and Applications-Volume 2. Springer Berlin
pieces?. Simon Wardley. Archived from the original (HTML) on 8 March 2016. Heidelberg, 2013. 619-626.
Retrieved 29 December 2016. 23. ^ Flower, Zachary. "Weigh the benefits of PaaS providers against lock-in risks" .
6. ^ Zimki, hosted JavaScript environment, http://radar.oreilly.com/2006/09/zimki-hosted- searchcloudcomputing.techtarget.com. Retrieved 21 November 2018.
javascript-enviro.html 24. ^ a b Kavis, Mike. "Top 8 Reasons Why Enterprises Are Passing On PaaS" . Forbes.
7. ^ What is a pre-shaved Yak, 25. ^ "James Somers (Ft. Andrew Warner, ATodd, Chrissy & Tom Lehman) – Heroku's Ugly
https://www.flickr.com/photos/zimki/243779431/in/photostream/ Secret" . Genius.
8. ^ Pre Shaved Yaks, http://archive.ianwinter.co.uk/2007/09/25/zimki-is-no-more/ 26. ^ Andrew C. Oliver, "Which freaking PaaS should I use?" InfoWorld, October 8, 2012.
9. ^ "Server-Side JavaScript" . developer.mozilla.org. August 25, 2018. 27. ^ Jason Brooks, "Apprenda 3.0 Brings Private PaaS to .NET Developers," eWeek,
10. ^ Fotango Opens its APIs, http://www.prnewswire.co.uk/news-releases/fotango-opens- January 6, 2012.
its-zimki-customer-api-153777895.html 28. ^ Anthony Wing Kosner, "Developers in Demand: Platform As A Service Is Key to
11. ^ Fotango Opens its Zimki Customer API, http://www.prnewswire.co.uk/news- Growth of Mobile Cloud Computing," Forbes, June 8, 2012.
releases/fotango-opens-its-zimki-customer-api-153777895.html 29. ^ Yankee 2014 Predictions Mobility hits a tipping point Archived 2014-01-22 at the
12. ^ "There and back again ... a personal journey" . blog.gardeviance.org. April 22, 2009. Wayback Machine, Yankee Group, 2014.
13. ^ Zimki Shuts Down, http://blog.gerv.net/2007/09/zimki_shuts_down/ 30. ^ Christina Warren, "How to Pick a Server for Your App," Mashable, November 16,
14. ^ "Zimki closure shows the perils of hosted web platforms" . 2011.
15. ^ OSCON Keynote 2007, http://mais.uol.com.br/view/v1xaxe2lamb3/oscon-- 31. ^ "Interview With Brian Sullivan – Inventor of Open Platform As A Service," Archived
commoditisation-of-it-and-what-the-future-holds-0402D4B10386?types=A 2013-10-04 at the Wayback Machine sullivansoftwaresystems.com, 2010.
16. ^ a b Jack Schofield, "Google angles for business users with ‘platform as a service’," 32. ^ Nancy Gohring, "Platform as a service heats up," Computerworld, July 8, 2013.
The Guardian, April 16, 2008.

· · Cloud computing [hide]

Content as a service · Data as a service · Desktop as a service · Function as a service · Infrastructure as a service · Integration platform as a service ·
As a service
Mobile backend as a service · Network as a service · Platform as a service · Security as a service · Software as a service
Cloud database · Cloud storage · Data centers · Distributed file system for cloud · Hardware virtualization · Internet · Native cloud application · Networking · Security ·
Technologies
Structured storage · Virtual appliance · Web APIs · Virtual private cloud
Applications Box · Dropbox · Google (Workspace · Drive) · HP Cloud (closed) · IBM Cloud · Microsoft (Office 365 · OneDrive) · Oracle Cloud · Rackspace · Salesforce · Workday · Zoho

Alibaba Cloud · Amazon Web Services · AppScale · Box · Bluemix · CloudBolt · Cloud Foundry · Cocaine (PaaS) · Creatio · Engine Yard · Helion · GE Predix ·
Platforms Google App Engine · GreenQloud · Heroku · IBM Cloud · Inktank · Jelastic · Mendix · Microsoft Azure · MindSphere · Netlify · Oracle Cloud · OutSystems · openQRM ·
OpenShift · PythonAnywhere · RightScale · Scalr · Force.com · SAP Cloud Platform · Splunk · VMware vCloud Air · WaveMaker
Alibaba Cloud · Amazon Web Services · Abiquo Enterprise Edition · CloudStack · Citrix Cloud · CtrlS · DigitalOcean · EMC Atmos · Eucalyptus · Fujitsu · GoGrid ·
Google Cloud Platform · GreenButton · GreenQloud · IBM Cloud · iland · Joyent · Linode · Lunacloud · Microsoft Azure · Mirantis · Netlify · Nimbula · Nimbus · OpenIO ·
Infrastructure
OpenNebula · OpenStack · Oracle Cloud · OrionVM · Rackspace Cloud · Safe Swiss Cloud · SoftLayer · Zadara · libvirt · libguestfs · OVirt · Virtual Machine Manager ·
Wakame-vdc · Virtual Private Cloud OnDemand

Category · Commons

Categories: As a service Cloud platforms

This page was last edited on 26 August 2021, at 11:14 (UTC).

Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered
trademark of the Wikimedia Foundation, Inc., a non-profit organization.

Privacy policy About Wikipedia Disclaimers Contact Wikipedia Mobile view Developers Statistics Cookie statement