The document provides an overview of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It discusses the history and evolution of cloud computing. It then describes the key characteristics and benefits of IaaS, PaaS and SaaS. For each layer, examples of common providers are given. Reasons for using PaaS over self-managed infrastructure are explained, such as faster time to market and lower costs. Considerations for choosing a PaaS provider are also outlined.

1. *aaS 101
- All about IaaS, PaaS and SaaS

2. About Me
29/01/2015 2

3. Agenda
• History of Cloud Computing
• What is Cloud Computing
• Cloud Services Layers
• Why use PaaS
• Providers
29/01/2015 3

4. History of Cloud Computing
• 1960 time sharing was developed to allow multiple users to use
computers
29/01/2015 4

5. History of Cloud Computing
• 1969 ARPA net was launched
29/01/2015 5

6. History of Cloud Computing
• 1977 The Personal Computing Revolution begins. Microcomputers
begin to be available on the mass market.
29/01/2015 6

7. History of Cloud Computing
• 1990s The infrastructure starts to develop, fast broadband became
more widespread. This allowed applications to be delivered over the
internet
29/01/2015 7

8. History of Cloud Computing
• 1996 George Favaloro a Compaq marketing executive and Sean
O’Sullivan were writing a business plan for “internet business” and
they called it “cloud computing”
29/01/2015 8

9. History of Cloud Computing
• 1997 professor Ramnath Chellappa from University of Texas uses the
term “cloud computing” for the first time in a scientific paper, in his
presentation “Intermediaries in Cloud-Computing: A New Computing Paradigm”
29/01/2015 9

10. History of Cloud Computing
• 1998 VMware – a company which provides virtualization software is
founded.
29/01/2015 10

11. History of Cloud Computing
• 1999 Salesforce.com was founded. It was the first cloud-based SaaS
solution. It revolutionized enterprise software by delivering it via a
website, and not on physical medium.
29/01/2015 11

12. History of Cloud Computing
• 2002 Amazon Web Services was launched
• 2006 Amazon Elastic Compute Cloud –EC2 allowed pay per use for
computing power
29/01/2015 12

13. History of Cloud Computing
• 2007 Microsoft starts project Red Dog
29/01/2015 13

14. History of Cloud Computing
• 2009 Google Apps suite was launched
29/01/2015 14

15. History of Cloud Computing
• 2010 project Red Dog became commercially available, and is renamed
to Windows Azure
29/01/2015 15

16. What is Cloud Computing
“Cloud computing, often referred to as simply the cloud,
is the delivery of on-demand computing resources—everything from
applications to data centers—over the Internet on a pay-for-use basis.” - IBM
29/01/2015 16

17. What is Cloud Computing
• Elastic resource
• You can scale up/ down based on your needs
• Pay per use
• You pay only for what you use
• Self services
• You can access all the IT resources needed yourself
29/01/2015 17

18. What is this presentation about?
29/01/2015 18

19. IaaS (Infrastructure as a Service)
Cloud Services Layers
SaaS (Software as a Service)
PaaS (Platform as a Service)
29/01/2015 19

20. • Offers servers in an easy to consume way
• You don’t have to care about:
• Networking
• Hard Drives
• Processors
• Memory
• Licenses
• Virtualization
• Electricity
• Cooling
• Floor space
• Physical security
• Physical maintenance
• Monitoring
• Backup
• You can make a remote desktop, and start installing software on the machine
• If you need additional resources (Memory, CPU, Space), just log in in the management
portal/console, and increase a number.
Networking
Storage
Servers
Virtualization
IaaS (Infrastructure as a Service)
29/01/2015 20

21. IaaS
• Target users: Sysadmins
• In a nutshell: hosts the application
• Providers:
• Rackspace.com
• AWS, EC2,S3
• Microsoft Azure (VM)
• Google compute engine (GCE)
• IBM Smart Cloud
• EMC
Networking
Storage
Servers
Virtualization
IaaS (Infrastructure as a Service)
29/01/2015 21

22. IaaS
• Bare bone virtual machines
Networking
Storage
Servers
Virtualization
IaaS (Infrastructure as a Service)
29/01/2015 22

23. IaaS
• Offers a solution for deploying applications or data
• You don’t have to care about:
• Operating System
• Application Servers
• Webservers
• Frameworks, SDKs
• Security Updates
• Load balancing
• Analytics
• Identity and Authorization
• You deploy your application from your IDE, or using the management
portal/console
• Usually offers a marketplace for extensions (provisioning a DB, Analytics ,
etc.)
OS
Middleware
Runtime
PaaS (Platform as a Service)
29/01/2015 23

24. IaaS
• Target users : Developers
• Providers:
• AWS Elastic Beanstalk
• Windows Azure (Websites, Cloud Services)
• Salesforce.com (Heroku, Force.com)
• Google App Engine
• IBM Bluemix
• Apache Stratos
• Oracle Cloud Platform
OS
Middleware
Runtime
PaaS (Platform as a Service)
29/01/2015 24

25. IaaS
OS
Middleware
Runtime
PaaS (Platform as a Service)
29/01/2015 25
• Deploy your application
• You can enable RDP

26. IaaS
OS
Middleware
Runtime
PaaS (Platform as a Service)
29/01/2015 26
• Deploy your website
• No RDP

27. • You already built the application, and you are offering to your
clients.
• The clients only need to do one thing: be online.
• You (the customer) don’t have to care about:
• Software
• Install
• Upgrades
• Maintenance
• Tuning
• App monitoring
Data
Applications
SaaS (Software as a Service)
29/01/2015 27

28. • Target users: Customers
• Providers:
• Salesforce.com
• Gmail
• Google Docs
• Office 365
• Citrix GoToMeeting
• Cisco WebEx
• XBOX Live
• WordPress
Data
Applications
SaaS (Software as a Service)
29/01/2015 28

29. • Allows developers to create quickly a backend (API) to which they
can connect from their web/ mobile app
• Usually offers out of the box
• User management
• Push notification
• Social services
• You don’t have to care about:
• Where this code is hosted
• Install
• Upgrades
• Security
• Tuning
• App monitoring
Data
Applications
BaaS(Backend as a Service)
29/01/2015 29

30. • Target users: Mobile/Web apps Developers
• Providers:
• Parse
• Appcelerator
• Kinvey
• Azure Mobile Services
Data
Applications
29/01/2015 30
BaaS(Backend as a Service)

31. Data
Applications
BaaS(Backend as a Service)
29/01/2015 31

32. Manage it yourself?
29/01/2015 32Networking
Storage
Servers
Virtualization
OS
Middleware
Runtime
Data
Applications

33. Networking
Storage
Servers
Virtualization
OS
Middleware
Runtime
Data
Applications
29/01/2015 33

34. Popularity
29/01/2015 34

35. Why use PaaS?
• Faster time to market
29/01/2015 35

36. Why use PaaS?
• Lower cost
• When demand fluctuates, how do we deal with this?
29/01/2015 37

37. Why use PaaS?
• Faster reaction time
• How quick can we scale up, and then down?
• What happens if we are not fast enough?
29/01/2015 38

38. Why use PaaS?
• Lower capital commitment
• Increase your resource as you need them
29/01/2015 39

39. Why use PaaS?
Focus on what is important (for dev’s):
• building apps
29/01/2015 40

40. Why NOT ?
• If this is the Holy Grail, why isn’t everyone using PaaS?
• Some reasons:
• “Don’t fix it if it is not broken”
• Converting legacy apps to PaaS is very complex, close to impossible
• Concerns about security
• Have a preference/requires tools that might not be integrated in a PaaS
• The required performance/hardware/network of the current PaaS solutions is
not good enough
29/01/2015 41

41. 29/01/2015 42

42. How do I choose a PaaS ?
29/01/2015 43

43. Microsoft Azure
• Launched on 1.February.2010
• Supports:
• .net
• Java
• Ruby
• Node.Js
• Python
• Php
• Dev env: visual studio OR
eclipse
29/01/2015 44

44. AppHarbor
• Launched on September 2010
• Supports:
• .net
29/01/2015 45

45. Bluemix - IBM
• Launched 30.June.2014
• Based on Softlayer and CloudFoundry
• Supports:
• .net (using Mono)
• Java
• Ruby
• Node.Js
• Python
• Scala
• Php
29/01/2015 46

46. What to look for in a PaaS provider
• Does it support your development language/framework ?
• What status is the PaaS in ? Beta? Production?
• What is the support model? What is the history of the company
offering the Paas?
• Can I extract my data from a running application (in order to move to
another provider)
• Am I locked-in by the services offered?
• Does it meet your requirements (performance, scalability, reliability)?
29/01/2015 47

47. 99.95%
29/01/2015 48

48. PaaS choices
Company Paas Name Supported Languages Launch Date
Amazon Elastic Beanstalk .net/ Java / Ruby / Node.Js
/Python/ Php
19.January.2011
AppHarbor AppHarbor .net September 2010
IBM Bluemix .net* Java / Ruby / Node.Js
/ Python / Scala / Php
30.June.2014
Microsoft Azure .net / Java / Ruby / Node.Js
/ Python /Php
1.February.2010
Red Hat Open Shift .net*/ Java / Ruby/ Node.Js
/ Perl /Python / Php
4.May.2011
29/01/2015 49
* Using Mono

49. 29/01/2015 50