On the future--paas of cloud computing from seven aspects

Most Web applications will eventually be used on Platform-as-a-service, PAAs. Such a change would be slower for infrastructure as a service (IaaS), because the development of a perfect PAAs would greatly lose control of the hardware and software. Many IT companies will boycott it, but PAAs services will eventually occur.

Positioning the PAAs value is very simple: with your code, we will serve you all-Internet connectivity, power, hardware, operating system, software, monitoring, backup, recovery, failover, scaling, and more. The IT department is focused on writing code to solve business problems, leaving vendors with infrastructure and operational mechanisms. In theory, you'll get a better practice deployment, including security and business continuity, with lower costs and better quality, compared with your own employees.

We're talking about "theory" because these are all in the early stages, and as vendors offer a variety of different services to more mobile devices, CIOs need time to prove their stability. We believe, however, that PAAs is a future trend that does not take into account that PAAs companies will eventually be disadvantaged.

The enterprise should consider the seven major factors of PAAs:

The implementation of PAAs requires two main factors: one is platform service, the other is running platform. We include PAAs vendors in our comparisons, which must sell both software and SaaS services on a Web application and provide an infrastructure to run these applications on. If the vendor does not provide the underlying infrastructure beyond the platform, you will not fully reflect the true value of PAAs, because you lack the "one pack in the end" experience.

PAAs vendors are much more difficult than IaaS or SaaS vendors because there are many different factors. We have an in-depth discussion and assessment of this in the article. Here we have a seven-factor assessment of how to select a PAAs provider.

Programming languages and frameworks: it typically has a preferred programming language, and vendors rarely support the language's operation. But one exception: proprietary PAAs, customer purchases are based on other factors and are required to be willing to use any language. The best example is Salesforce.com's force.com, which uses a proprietary language, but provides a powerful ecosystem on top of the application developer's brain compared to the traditional application development platform.

Database: Generally, PAAs database server support is similar to programming language support. However, modern application development is mitigated by migrating to different database servers. Several PAAs providers also support so-called "next-generation" databases, such as Xeround, which provide a widely used database of the same interface, like MySQL, but only as a service provider. To ensure that they meet your regulatory and security policy requirements, the security of critical validation databases is provided by PAAs vendors.

Usability: Shrinking your list is based on programming language and database support, and then the next definition should be how to save your application uptime. To do this, we ask some questions about our surroundings to see what happens when the server and software fail. The service Level agreement (SLA) is important, but it almost never pays for enterprise application downtime. Finally, in terms of cost revenue from SLA vendors, the vendor will clearly define the service content and responsibilities that are required to be responsible.

Security: Security and regulatory rules are critical when vendors choose the infrastructure, and PAAs is the same. Keep in mind that multitasking is a trend for a wide range of suppliers--paas vendors want to reduce costs and maintain high availability, it is necessary to spread a large number of applications and data on the shared server. This has led to a PAAs application that is outside the scope of regulation, but many vendors already have solutions to common regulation, like storing credit cards.

Services: Many PAAs vendors offer additional services, such as additional products from third parties. There are these: Code library integration (starting the application's Source repository branch)??, caching services (saving database query results to speed up application), logging Service (to consolidate all application copy logs) and payment services (outsourced acceptance, processing and storage of credit card numbers in a PCI compliant environment).

Customer Service: The PAAs service establishes services between tiers (for example, from the application layer to the database tier), which makes developers and suppliers more closely connected.

Price: Cost is of course important, so it's more cost-efficient than other options, such as in-house deployments or Iaas,paas. To migrate to your existing deployment, PAAs services have only a small price difference compared to other services. We want to get the most appropriate language, database, and load support with security and availability-compliant services.

Note that the PAAs price is proportional to the actual cost. Highly optimized application code is more efficient than application code that has not been optimized. Similarly, if you choose to run on a vendor-product application, the vendor may ask you to purchase more service items that are not predictable until an application is run. Fortunately, most PAAs factory chambers offer a free trial. So finally, please make sure you can use other applications in the event of a different vendor price increase or service disruption.