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 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 infrastructure typically associated with developing and launching the application(s), and to allow developers to create, develop, and package such software bundles.[1] [2]
PaaS can be delivered in three ways:
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 March 2006 and a public launch at EuroOSCON in 2006.[6]
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 the perils of being dependent on a single provider.[7] 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. [8]
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.[9]
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] [10] Development tools provided by the vendor are customized according to the needs of the user.[11] 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.[12] [13]
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,[14] lack of operational features,[15] reduced control,[15] and the difficulties of traffic routing systems.[16]
There are several types of PaaS, including public, private and hybrid.[9] PaaS was originally intended for applications on public cloud services, before expanding to include private and hybrid options.[9]
Public PaaS is derived from software as a service (SaaS),[17] 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.[18]
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.[19]
Hybrid PaaS is typically a deployment consisting of a mix of public and private deployments.
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.[20] 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 PBX, cellular networks, (near real-time) applications typically are deployed on CPaaS platforms.
Initiated in 2012, mobile PaaS (mPaaS) provides development capabilities for mobile app designers and developers.[21] The Yankee Group identified mPaaS as one of its themes for 2014.[22] [23]
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.[24]
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.[25] 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.[26]