Introduction to migration to cloud

(1)

Project acronym: NEBULA

Project name: A novel vocational training programme on cloud computing skills Project code: 540226-LLP-1-2013-1-GR-LEONARDO-LMP

Document Information

Document ID name: Nebula_WP4_D4.3.1_Learning_Material_and_Content_2015_30_04

Document title: Nebula VET program learning material and content

Type: Slides

Date of Delivery: 30/04/2015

Work package: WP4

Activity D.4.3.1

Dissemination level: Public

Document History

Versions Date Changes Type of change Delivered by

Version 1.0 15/04/2015 Initial Document - UCBL and INSA of Lyon

Version 2.0 23/06/2015 Edition to feedback provided byModifications according

partners UCBL and INSA of Lyon Version 2.1 02/09/2015 Edition Insertion of license type UCBL and INSA of Lyon

Acknowledgement

The persons of UCBL in charge of producing the course are Parisa Ghodous, Catarina Ferreira Da Silva, Jean Patrick Gelas and Mahmoud Barhamgi. The persons from UCBL involved in preparing, translation and review are Hind Benfenatki, Gavin Kemp and Olivier Georgeon.

The persons of INSA of Lyon in charge of producing the course are Frédérique Biennier, Nabila Benharkat. The person from INSA of Lyon involved in preparing, translation and review is Youakim Badr.

Disclaimer

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.

This publication reflects the views only of the author, and the Commission cannot be held responsible for any use, which may be made of the information contained therein.

(2)

Introduction to migration to cloud

Objectives

Define the fundamental concepts that are associated to

cloud computing and migration to the cloud, identifying

the most relevant opportunities and general benefits

---Note: due to intellectual property reasons, the logotype of UCBL

must remain in all utilisation of this course content, as well as the

note “copyright DUNOD” mentioned in some slides with figures.

(3)

Introduction to migration to cloud

(4)

PART 4 OVERVIEW

1. PaaS

(5)

What does PaaS mean?

• PaaS means Platform as a Service or platform of

cloud computing

• This term means an execution platform hosted

by an operator and accessed by Internet

• Amazon Web Services (AWS) is the first

platform of cloud computing

• PaaS approach, not only provides a deported

execution environment but also a set of

(6)

PaaS Characteristics (1/2)

• Allows a cloud user to deploy consumer-created or

acquired applications using programming languages and

tools supported by the service provider

• Provides specific programming languages support, APIs,

development environments, database instances,

computation instances, application server instances

• Not particularly useful when:

– Proprietary programming languages are used

– The hardware and software must be customized, for

instance to improve the performance of the application

(7)

PaaS Characteristics (2/2)

The user (i.e. the developer):

– Has control over the deployed applications and, possibly,

application hosting environment configurations

– Does not manage or control the underlying cloud

infrastructure including network, servers, operating systems,

or storage

(8)

Multiple PaaS types

• PaaS platforms propose:

• Data persistence service

• Application hosting service

• Integration service

• Monitoring service

Integration

Application

Execution

Data

Persistence

Copyright DUNOD

Users

Integration

Application

Execution

Data

Persistence

(9)

PaaS Specificities

• Virtualization

• CAP Theorem (Consistency, Availability and

Partition Tolerance): it is possible for a web

distributed computer system to simultaneously

satisfy only two of the three following guarantees:

– Consistency: a processing keeps all of the data in a

coherent state

– Availability: capacity of system to offer a constant service

quality to users

– Partition-tolerance: capacity of the system to function

even one of the component fails

(10)

PaaS components

• Data center

• Persistence level

• Execution level on virtual machine or

runtime

• Integration level: API or Integration Bus

• Composition level in form of company’s

(11)

Some considerations on migration to PaaS

providers

• Independence between IT on-premises

infrastructure and PaaS offerings

• Redesign the software architecture

• Adopt a service-oriented architecture

• Need of experienced software architects to

understand how best to integrate both

on-premises and the selected PaaS offerings

information systems

(12)

Major PaaS players

• Amazon Web Services

– Examples: Elastic MapReduce (EMR) and S3 storage

• Google App Engine

– AppScale offers an open-source cloud computing platform

for Google App Engine applications

• Microsoft Azure

– Environment for execution of applications and persistent

storage

– AppFabric connects users and on-premises applications

to cloud-hosted applications

(13)

Other Powerful PaaS Providers

• Web application development and deployment

– Engine Yard uses the languages Ruby on Rails, PHP and

the runtime environment Node.js

– Cloud Foundry uses Java, Ruby, Python, Go, PHP or

Node.js

• Virtual servers where customers can install their own

operating systems

(14)

Other Powerful PaaS Providers

• Process data & apps in real time

– Gigaspaces XAP (eXtreme Application

Platform) application server using in-memory

data grid caching

• Force.com’s AppExchange and Heruko

platform

• Appistry's CloudIQ

(15)

Lifecycle of application development on

PaaS platform

(16)

When to develop on PaaS platform?

Today, we consider the development on

PaaS platform is justified only if the qualities

of this platform bring more benefits for

company, such as:

• High availability offered by platform

• Security on data integrity

• Capacity of absorption of seasonal surcharge

• Capacity to store large amounts of data

(17)