23-03-2011, 04:18 PM
Presented by:
Stuart Charlton
[attachment=10864]
Cloud Computing and the Next Generation of Enterprise Architecture
Objectives
Does cloud computing change the importance and role of enterprise architecture and
IT service management?
Exploring a reference model for the cloud
Suggesting a way to bridge the gap between architectural intent and results through cloud computing
What do you mean by... architecture?
Architecture
» The fundamental organization of a system, embodied in its components, their relationships to each other, and the environment, and the principles governing its design and evolution.
(ISO 42010 / IEEE 1471-2000 definition)
Enterprise Architecture
» Enterprise Architecture is the organizing logic for businesses and their IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
Peter Weill, MIT
Architecture as Strategy
• A Gap in Realizing Architectural Goals
How have we managed our IT?
Developer-led
» Concurrent Versioning, Unit Testing, Maven, Ant, Capistrano
» Focused on code-promotion ; sometimes database transform
Manager-led
» One extreme: firefighting
» The other extreme: bureaucracy
Architect-led
» Round-trip modeling tools (e.g. Rational UML, Together, etc.)
» Gated reviews (i.e. “The technology cops”)
Operations-led
» Management suites (OpenView, Tivoli, etc.)
» Runbook Automation (e.g. HP/OpsWare, BMC/BladeLogic, Opalis)
IT Infrastructure Library (ITIL) v3:
The Current Best Practice?
How Far Can Technology Save Us?
The “Google Secret Sauce” Theory:
» Always available, scalable, fast
» Computing as fungible commodity
» Reliability is enabled by architecture
» But you have to rewrite your software
Does a seemingly magical architecture reduce or eliminate the need for configuration & dependency management?
Does this architecture match classic enterprise requirements?
• The Cloud Provider Continuum
• Qualities of an Enterprise Cloud
• On-Demand, Services-Oriented Computing
» Drastically reduced lead times
» Lowered requirement to call-ahead forecasts
» Demand trends are predicted by the provider
• Variable cost consumption
» Pay-by-the-drink or over time; decouple fixed overhead from demand
• Self-service
» Resources directly/indirectly reserved with a GUI or API
• Elastic Scalability
» Grow or shrink resources as required
• Mandatory Network
» The network is essential to consume the service
• Governance and Compliance
» Tracking and matching of cloud providers to policies
Stuart Charlton
[attachment=10864]
Cloud Computing and the Next Generation of Enterprise Architecture
Objectives
Does cloud computing change the importance and role of enterprise architecture and
IT service management?
Exploring a reference model for the cloud
Suggesting a way to bridge the gap between architectural intent and results through cloud computing
What do you mean by... architecture?
Architecture
» The fundamental organization of a system, embodied in its components, their relationships to each other, and the environment, and the principles governing its design and evolution.
(ISO 42010 / IEEE 1471-2000 definition)
Enterprise Architecture
» Enterprise Architecture is the organizing logic for businesses and their IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
Peter Weill, MIT
Architecture as Strategy
• A Gap in Realizing Architectural Goals
How have we managed our IT?
Developer-led
» Concurrent Versioning, Unit Testing, Maven, Ant, Capistrano
» Focused on code-promotion ; sometimes database transform
Manager-led
» One extreme: firefighting
» The other extreme: bureaucracy
Architect-led
» Round-trip modeling tools (e.g. Rational UML, Together, etc.)
» Gated reviews (i.e. “The technology cops”)
Operations-led
» Management suites (OpenView, Tivoli, etc.)
» Runbook Automation (e.g. HP/OpsWare, BMC/BladeLogic, Opalis)
IT Infrastructure Library (ITIL) v3:
The Current Best Practice?
How Far Can Technology Save Us?
The “Google Secret Sauce” Theory:
» Always available, scalable, fast
» Computing as fungible commodity
» Reliability is enabled by architecture
» But you have to rewrite your software
Does a seemingly magical architecture reduce or eliminate the need for configuration & dependency management?
Does this architecture match classic enterprise requirements?
• The Cloud Provider Continuum
• Qualities of an Enterprise Cloud
• On-Demand, Services-Oriented Computing
» Drastically reduced lead times
» Lowered requirement to call-ahead forecasts
» Demand trends are predicted by the provider
• Variable cost consumption
» Pay-by-the-drink or over time; decouple fixed overhead from demand
• Self-service
» Resources directly/indirectly reserved with a GUI or API
• Elastic Scalability
» Grow or shrink resources as required
• Mandatory Network
» The network is essential to consume the service
• Governance and Compliance
» Tracking and matching of cloud providers to policies
