Easy technology setup Little control over deployment, Software as a Service (SaaS) upgrade and testing methodology applications running on Rapid deployment Providers’ cloud infrastructure are accessed Likely limitations on amount of No upfront capital investment through thin-client (e.g. web customisation and tailoring browser) or program interfaces. Typically stable software Data privacy issues and difficulties in return of customer data Most cost effective model as only the software is leased Integration can be difficult and unsupported (although this is becoming less common with the rise of open APIs) Platform as a Service (PaaS) No need for capital hardware More management effort due to investment responsibility for application Customer-created or purchased updates and upgrades applications are deployed onto a Rapid deployment cloud infrastructure. Likely to be a shared platform, provider’s Support for integration requiring security considerations Data privacy issues Not as cost effective as SaaS Removes the need to buy, house Most expensive Infrastructure as a Service (IaaS) and maintain physical servers Computer infrastructure Responsibility for Virtual Machine (processing, storage, networks Ability to respond quickly to Management etc) are provided to the customer, changing demand Need for new skills sets and to deploy their own software Greater level of control over Virtual regular training program to keep applications. Machine step with technology changes Simplifies integration Responsibility for backups There are four common deployment models: Model Potential Advantages Potential Disadvantages Private cloud More control Typically more expensive Cloud infrastructure is provisioned Good data security and Lower economies of scale for exclusive use by a single compliance Lower resilience
Software as a Service (SaaS) Providers’ applications running on cloud infrastructure are accessed through thin-client (e.g. web browser) or program interfaces. Easy technology setup Rapid deployment No upfront capital investment Typically stable software Most cost effective model as only the software is leased Little control over deployment, upgrade and testing methodology Likely limitations on amount of customisation and tailoring Data privacy issues and difficulties in return of customer data Integration can be difficult and unsupported (although this is becoming less common with the rise of open APIs) Platform as a Service (PaaS) Customer-created or purchased applications are deployed onto a provider’s cloud infrastructure. No need for capital hardware investment Rapid deployment Support for integration More management effort due to responsibility for application updates and upgrades Likely to be a shared platform, requiring security considerations Data privacy issues Not as cost effective as SaaS Infrastructure as a Service (IaaS) Computer infrastructure (processing, storage, networks etc) are provided to the customer, to deploy their own software applications. Removes the need to buy, house and maintain physical servers Ability to respond quickly to changing demand Greater level of control over Virtual Machine Simplifies integration Most expensive Responsibility for Virtual Machine Management Need for new skills sets and regular training program to keep step with technology changes Responsibility for backups There are four common deployment models: Model Potential Advantages Potential Disadvantages Private cloud Cloud infrastructure is provisioned for exclusive use by a single More control Good data security and compliance Typically more expensive Lower economies of scale Lower resilience
G3.4%20Cloud%20Services%20Planning%20Guideline%20V1.1%20Beta.docx