Platform as a service

[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.

[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.

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.

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.

[9] PaaS was originally intended for applications on public cloud services, before expanding to include private and hybrid options.

[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.

Some open platforms let the developer use any programming language, database, operating system or server to deploy their applications.