
Anyway, who wants to deal with the IT folks and deal with all the tantrums they throw, what is possible and what is not.
Bernard Golden, in his article "What You Need to Know About PaaS" talks about the various issues that need to be looked at, when selecting your PaaS vendor.
- Lock-in - The productivity gains you get by using vendor API's also mean you get locked on to the platform and application migration becomes all the more difficult.
- Complexity - Writing PaaS application is not the same as writing regular applications. Depending on the vendor, the complexity of writing application increases as you try to add more functionality
- Cloud Service Provider Differentiation - The whole premise of PaaS platform is to make the writing of applications easy. With all the abstraction the platform provide, you end up getting locked at operation level
- New Skills - PaaS platforms require new set of skills which means either re-train your existing employee or hire new people
- Mapping existing practices to new frameworks - Every enterprise will have standard processes, tools and methodologies of working and developing applications. All these need to be re-looked based on the PaaS platform
All in all, PaaS platforms need to be evaluated based on your requirements and fitment as per your organisation needs.
Read the complete article here.
Bernard presents a good Enterprise Architecture focused checklist for a Cloud journey. An evaluation framework can help architects evaluate and select PaaS offerings. The evaluation framework can be used to shortlist PaaS providers, build questions posed in the Request for Proposal document, or generate use case scenarios. What are your thoughts about the 7 categories and 80+ evaluation criterion found within the 'Selecting a Cloud Platform' white paper found at
http://wso2.com/casestudies/selecting-a-cloud-platform/
Post a Comment