PaaS offerings facilitate deployment of applications without the cost and complexity of buying and managing the underlying hardware and software and provisioning hosting capabilities, 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.
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.
- 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.
- Services to develop, test, deploy, host and maintain applications in the same integrated development environment
Different PaaS offerings provide different combinations of services to support the application development lifecycle. Comprehensive PaaS should provide all service options in an integrated development environment within the actual target delivery platform, with source code control, version control, dynamic (interactive) multiple user testing, roll out and roll back with the ability to audit and track who made what changes when to accomplish what purpose
- Web based user interface creation tools
- Multi-tenant architecture
PaaS offerings typically attempt to support use of the application by many concurrent users, by providing concurrency management, scalability, failover and security. The architecture enables defining the “trust relationship” between users in security, access, distribution of source code, navigation history, user (people and device) profiles, interaction history, and application usage.
- Integration with web services and databases
Support for SOAP and REST interfaces allow PaaS offerings to create compositions of multiple Web services, sometimes called “Mashups” as well as access databases and re-use services maintained inside private networks. Support for keeping the user/relationships (if multiple users)/device context and profile through the mashup across web services, databases and networks.
- Support for development team collaboration
The ability to form and share code with ad-hoc or pre-defined or distributed teams greatly enhances the productivity of PaaS offerings. Schedules, objectives, teams, action items, owners of different areas of responsibilities, roles (designers, developers, tester, QC) can be defined, updated and tracked based on access rights.
- Utility-grade instrumentation
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 &/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 few.
Financial data collection and, possibly, forecasting, are required to determine who pays what to whom and when (how often).
FREE eBook Gift for Signing Up
Get Your FREE eBook
Subscribe to Robert's mailing list and get a FREE eBook offer.
Thank you for subscribing.
Something went wrong.