Beruflich Dokumente
Kultur Dokumente
PaaS offerings facilitate deployment of applications without the cost and complexity of buying and managing the underlying hardware and software and provisioning hosting capabilities[1], providing all of the facilities required to support the complete life cycle of building and delivering web applications and services entirely available from the Internet[2]. PaaS offerings may include facilities for application design, application development, testing, deployment and hosting as well as application 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. These services may be provisioned as an integrated solution over the web.
Contents
[hide]
1 Types 2 Key characteristics 3 PaaS Products and Services 4 See also 5 References
[edit] Types
Add-on development facilities These facilities allow customization of existing SaaS applications, and in some ways are the equivalent of macro language customization facilities provided with packaged software applications such as Lotus Notes, or Microsoft Word. Often these require PaaS developers and their users to purchase subscriptions to the co-resident SaaS application. Stand alone development 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. Application delivery-only environments Some PaaS offerings lack development, debugging and test capabilities, and provide only hosting-level services such as security and on-demand scalability. Open Platform as a Service Lets the developer use any programming language, any database, any operating system, any server, etc. [3]
PaaS offerings provide developers insight into the inner workings of their applications, and the behavior of their users. Some PaaS offerings use information about user behaviour to enable pay-per-use billing. Historical/usage evidence may help:
determine whether services are of value to users/customers, compare the value of different services, and track activity based costs and revenues.
Visualization tools could show usage patterns, exposing functional or correlational relationships between:
services and/or user interactions, the value to the user or users, and the cost of alternative service paths such as web and cell phone
just to name a couple. Financial data collection and, possibly, forecasting, are required to determine who pays what to whom and when (how often).