SlideShare a Scribd company logo
David S. Linthicum, CTO [email_address] @DavidLinthicum Moving to Cloud Computing Step-by-Step
UNDERSTANDING THE RELATIONSHIPS SOA Cloud Computing Enterprise Architecture
SOA AND CLOUD COMPUTING One can consider cloud computing the extension of SOA out to cloud-delivered resources, such as storage-as-a-service, data-as-a-service, platform-as-a-service -- you get the idea.  The trick is to determine which services, information, and processes are good candidates to reside in the clouds, as well as which cloud services should be abstracted within the existing or emerging SOA. Cloud Computing Services On-Demand Database On-Demand Applications On-Demand Platform On-Demand SOA Shared Services Shared Information Shared Processes Agility Integration Governance
THREE LAYERS OF CLOUD COMPUTING Software as a Service (SaaS) Finished applications that you rent and customize Platform as a Service (PaaS) Developer platform that abstracts the infrastructure, OS and middleware to drive developer productivity Infrastructure as a Service (IaaS) Deployment platform that abstracts the infrastructure
THE "CLOUD PYRAMID" Describes Cloud Services Economy Building blocks: IaaS -> PaaS -> SaaS Source:  GoGrid Google App Engine
NIST defines cloud computing as a set of characteristics, delivery models, and deployment models On-demand self-service   Ubiquitous network access   Resource pooling Rapid elasticity Pay per use 5 Characteristics Software as a Service (SaaS)   Platform as a Service (PaaS) Infrastructure as a Service (IaaS) 3 Delivery Models Private Cloud Community Cloud Public Cloud Hybrid Cloud 4 Deployment Models
“THE CLOUD”? Size of the cloudlets and overlap shown is not to scale  Shared application infrastructure as a service (AIaaS) Application platform  as a service (APaaS) IaaS – Integration as a service Off-Premises Cloud Infrastructure Utility Hosting Web Hosting SaaS AIaaS APaaS IaaS Cloud Platform Native Web  Applications Hardware  managed by  others Elastic Internet  resources Fixed, dedicated  resources Shared  applications Provider-dedicated Web  applications and Web  content Commodity  (industrialized)  computing resources Hosted dedicated  Web applications  and Web content Programmable or  programmatically  accessible resources Source: Gartner Research
ORGANIZING THE CLOUDS Infrastructure-as-a-Service Security-as-a-Service Storage-as-a-Service Integration-as-a-Service Database-as-a-Service Information-as-a-Service Process-as-a-Service Platform-as-a-Service Application-as-a-Service Management/Governance-as-a-Service Testing-as-a-Service
WHY CLOUD? THE EXISTING TRAJECTORY IS NOT GOOD WHY CLOUD? $ Capability
UNDERSTANDING THE ROI
$500,000 $1,000,000 On-Premise
Cloud Delivered
“ For the cloud, we're all in.”
CLOUD POPULARITY=HYPE Source: CA
NEED A JOB?
CRAZY CLOUD WASHING
FEAR OF MULTITENANCY
 
A “Connectivity Explosion” Applications, formats, APIs, protocols, standards, etc. Connected business partners Connectivity neither trivial nor static: Incompatible structures, semantics, business rules No  mature standards Changes abound Not easy to create robust Web services interfaces Connectivity becomes more challenging than ever Source:  Pervasive Software
Data volumes increases at an explosive rate 1 Exabyte = 1 quintillion bytes 2010 2009 2008 2007 (IDC) Data subject to Sarbanes-Oxley, Basel II or other governmental regulation
 
Standalone cloud Cloud 1 Cloud 2 enterprise Extended enterprise cloud Cloud 1 Cloud 3 Cloud 2 Intercloud Cloud Source:  Bob Grossman
CLOUD ABSTRACTION Cloud B Cloud C Cloud A Task Routing
Local data center (small, dedicated) Remote cloud  (large, pay per use) Dynamic Workload User requests User requests Workload factoring HYBRID CLOUDS Source:  NEC
HERE WE GO AGAIN?
“ Cloud-computing will help to optimize the Federal data facility environment and create a platform to provide services to a broader audience of customers.” President’s Budget for FY 2010 Section 9, Cross Cutting Programs
IT IS SKEPTICAL IT is understandably skittish about cloud computing. However, many of the cloud computing resources out there will actually provide better service than on-premise. Security and performance are still issues. Also, control.
SECURITY AND MATURITY TOP LIST OF CONCERNS FOR CLOUD SERVICES
CONSIDER PRIVATE CLOUDS “ Private Cloud Computing is Real  – Get Over It”    -  Tom Bittman – Gartner
CONSIDERING CLOUDS However, not so fast. Not all computing resources should  exist in the clouds, private or public. Cloud computing is not always cost effective. Do your homework before making the move.
CLOUD COMPUTING A Fit When: Processes, applications, and data are largely independent Points of integration are  well defined Lower level of security is fine Core internal enterprise  architecture is healthy Web is the  desired platform Cost is an issue Applications are new Not A Fit When: Processes, applications, and data are largely coupled Points of integration are  not well defined Higher level of security is required Core internal enterprise architecture needs work The application requires  a native interface Cost is an issue Application is legacy
PATH TO THE CLOUDS Path to clouds: start with the architecture Understand: Mission drivers Information under management Existing services under management Core business processes
“AS-IS”
“TO BE”
DEPLOY
INFORMATION MODEL
SERVICE MODEL
STEPPING TO THE CLOUDS
DON’T FORGET Episode 100 Last Week!
THANKS! David S. Linthicum [email_address]

More Related Content

Moving to cloud computing step by step linthicum

  • 1. David S. Linthicum, CTO [email_address] @DavidLinthicum Moving to Cloud Computing Step-by-Step
  • 2. UNDERSTANDING THE RELATIONSHIPS SOA Cloud Computing Enterprise Architecture
  • 3. SOA AND CLOUD COMPUTING One can consider cloud computing the extension of SOA out to cloud-delivered resources, such as storage-as-a-service, data-as-a-service, platform-as-a-service -- you get the idea. The trick is to determine which services, information, and processes are good candidates to reside in the clouds, as well as which cloud services should be abstracted within the existing or emerging SOA. Cloud Computing Services On-Demand Database On-Demand Applications On-Demand Platform On-Demand SOA Shared Services Shared Information Shared Processes Agility Integration Governance
  • 4. THREE LAYERS OF CLOUD COMPUTING Software as a Service (SaaS) Finished applications that you rent and customize Platform as a Service (PaaS) Developer platform that abstracts the infrastructure, OS and middleware to drive developer productivity Infrastructure as a Service (IaaS) Deployment platform that abstracts the infrastructure
  • 5. THE "CLOUD PYRAMID" Describes Cloud Services Economy Building blocks: IaaS -> PaaS -> SaaS Source: GoGrid Google App Engine
  • 6. NIST defines cloud computing as a set of characteristics, delivery models, and deployment models On-demand self-service Ubiquitous network access Resource pooling Rapid elasticity Pay per use 5 Characteristics Software as a Service (SaaS) Platform as a Service (PaaS) Infrastructure as a Service (IaaS) 3 Delivery Models Private Cloud Community Cloud Public Cloud Hybrid Cloud 4 Deployment Models
  • 7. “THE CLOUD”? Size of the cloudlets and overlap shown is not to scale Shared application infrastructure as a service (AIaaS) Application platform as a service (APaaS) IaaS – Integration as a service Off-Premises Cloud Infrastructure Utility Hosting Web Hosting SaaS AIaaS APaaS IaaS Cloud Platform Native Web Applications Hardware managed by others Elastic Internet resources Fixed, dedicated resources Shared applications Provider-dedicated Web applications and Web content Commodity (industrialized) computing resources Hosted dedicated Web applications and Web content Programmable or programmatically accessible resources Source: Gartner Research
  • 8. ORGANIZING THE CLOUDS Infrastructure-as-a-Service Security-as-a-Service Storage-as-a-Service Integration-as-a-Service Database-as-a-Service Information-as-a-Service Process-as-a-Service Platform-as-a-Service Application-as-a-Service Management/Governance-as-a-Service Testing-as-a-Service
  • 9. WHY CLOUD? THE EXISTING TRAJECTORY IS NOT GOOD WHY CLOUD? $ Capability
  • 13. “ For the cloud, we're all in.”
  • 18.  
  • 19. A “Connectivity Explosion” Applications, formats, APIs, protocols, standards, etc. Connected business partners Connectivity neither trivial nor static: Incompatible structures, semantics, business rules No mature standards Changes abound Not easy to create robust Web services interfaces Connectivity becomes more challenging than ever Source: Pervasive Software
  • 20. Data volumes increases at an explosive rate 1 Exabyte = 1 quintillion bytes 2010 2009 2008 2007 (IDC) Data subject to Sarbanes-Oxley, Basel II or other governmental regulation
  • 21.  
  • 22. Standalone cloud Cloud 1 Cloud 2 enterprise Extended enterprise cloud Cloud 1 Cloud 3 Cloud 2 Intercloud Cloud Source: Bob Grossman
  • 23. CLOUD ABSTRACTION Cloud B Cloud C Cloud A Task Routing
  • 24. Local data center (small, dedicated) Remote cloud (large, pay per use) Dynamic Workload User requests User requests Workload factoring HYBRID CLOUDS Source: NEC
  • 25. HERE WE GO AGAIN?
  • 26. “ Cloud-computing will help to optimize the Federal data facility environment and create a platform to provide services to a broader audience of customers.” President’s Budget for FY 2010 Section 9, Cross Cutting Programs
  • 27. IT IS SKEPTICAL IT is understandably skittish about cloud computing. However, many of the cloud computing resources out there will actually provide better service than on-premise. Security and performance are still issues. Also, control.
  • 28. SECURITY AND MATURITY TOP LIST OF CONCERNS FOR CLOUD SERVICES
  • 29. CONSIDER PRIVATE CLOUDS “ Private Cloud Computing is Real – Get Over It” - Tom Bittman – Gartner
  • 30. CONSIDERING CLOUDS However, not so fast. Not all computing resources should exist in the clouds, private or public. Cloud computing is not always cost effective. Do your homework before making the move.
  • 31. CLOUD COMPUTING A Fit When: Processes, applications, and data are largely independent Points of integration are well defined Lower level of security is fine Core internal enterprise architecture is healthy Web is the desired platform Cost is an issue Applications are new Not A Fit When: Processes, applications, and data are largely coupled Points of integration are not well defined Higher level of security is required Core internal enterprise architecture needs work The application requires a native interface Cost is an issue Application is legacy
  • 32. PATH TO THE CLOUDS Path to clouds: start with the architecture Understand: Mission drivers Information under management Existing services under management Core business processes
  • 38. STEPPING TO THE CLOUDS
  • 39. DON’T FORGET Episode 100 Last Week!
  • 40. THANKS! David S. Linthicum [email_address]