cloud computing and enterprise architecture for belgian ... · enterprise architecture for belgian...
TRANSCRIPT
Cloud Computing and
Enterprise ArchitectureEnterprise Architecture
for
Belgian Chapter
Association of Enterprise Architects
Martin van den Berg
Serviceline Manager Architecture
Sogeti Nederland
30 november 2011
Introduction Martin van den Berg
� Background:
� Business economics (Tilburg University)
� Master in Transport and Logistics Management (postdoc TIAS)
� Service Line Manager at Sogeti:
� Responsible for architecture service offerings and architecture
� Lead Architect in clientengagements:
� Support clients in engagements:
2Pagina 2
Master of Informatics
offerings and architecture craftmanship at Sogeti Netherlands
� Co-author of DYA and other books
� Chairman architecture section dutch computer society (Ngi)
� Member program board LAC
� Board of trustees CAEAP
� Current themes:
� Extended enterprise
� Cloud computing
� Demand management
� Business architecture
� Architecture and business themes
� Mobile
Email: [email protected]: bergmartLinkedin: http://nl.linkedin.com/in/mjbkvandenbergBlog: www.blog.sogeti.com
� Support clients in engagements: assessments, coaching, training, management, consultancy
� Recent engagements:
� FrieslandCampina: building EA Function
� ING: EA-assessments
� Rabobank: transition from rule-based to principle-based architecture
� Shell: lead EA for Shell E&P
3
http://cloud.sogeti.nl/Boek.aspx
EA and Cloud Computing
4
1. Is EA more important in case you want to make use of cloud services?
2. Will Cloud Computing lead to different types of EA artefacts?
3. Will Cloud Computing lead to a different way of doing EA?
Agenda
• Cloud Computing
• My view on Enterprise Architecture
• What is going on?
• What is the relationship between Cloud Computing and EA?
5
Computing and EA?
Agenda
• Cloud Computing
• My view on Enterprise Architecture
• What is going on?
• What is the relationship between Cloud Computing and EA?
6
Computing and EA?
What is Cloud Computing?
7
Cloud implementation models
8
Private Public
TraditionalDC
VirtualizedDC
In-house Private Cloud
Dedicated External Private
Cloud
Multi-tenant External Private
Cloud
ManagedPublic Cloud
Control
Economy of scale
High
Low
Low
High
Cloud servicemodels and characteristics
standardapp
standardapp
businessapp
businessapp
businessapp
standardapp
standardapp
standardapp
businessapp
businessapp
businessapp
standardapp
software
standardapp
businessapp
businessapp
presentationapplicationsdocumentsAPI’s
Salesforce.comMicrosoft Office365
Google AppsIBM LotusLive
Clo
udS
ervi
ces
9
infrastructure
middleware
middleware
middleware
infrastructure
platform
infrastructure
platform
datacenter facilitiesserverstoragenetworksecurity
Amazone EC2/S3IBM CloudBurst
VCE vBlockVMware vCloud
Microsoft Hyper-V Cloud
middlewareintegrationAPI’sprovisioningaccess
Force.comMicrosoft Azure
Google AppEngineVMware jCloud
IBM SMART Cloud
Clo
udC
ompu
ting
Clo
udS
ervi
ces
Cloud vs Non-Cloud
Middleware
Runtime
Data
Applications
Middleware
Runtime
Data
Applications
PaaS
Middleware
Runtime
Data
Applications
SaaSIaaS
Middleware
Runtime
Data
Applications
Traditional
10
Middleware
Network
Storage
Servers
Virtualisation
O.S.
Middleware
managed by consumer
Network
Storage
Servers
Virtualisation
O.S.
Middleware
Network
Storage
Servers
Virtualisation
O.S.
managed by cloud provider
Middleware
Network
Storage
Servers
Virtualisation
O.S.
11
Why Cloud?
Improved Accessibility
12
Accessibility
More Agility
Lower IT costs because of Economies of Scale
Innovation. Faster access to
new services
Why Cloud?
13
Source: Federal Cloud Computing Strategy, february 2011.
Who do make use of Cloud-services?
You and I,at home.On a largescale, withoutthinking twiceabout it.
Small & MediumEnterprisesOn a fairly large scale.Mostly public cloud likeSalesforce, Google,Facebook, LinkedIn.
14
Large EnterprisesOn a limited scale, but growing rapidly.Public & private Cloud.Examples: Ahold uses Google Apps worldwidePhilips uses 20 different cloud services like CRM, Collaboration, Purchasing, Computing
GovernmentOn a limited scale.In the process of defining strategy and conditions for a Government Cloud (community Cloud).
Cloud worries
Is it available?Who canaccess?
How to
15
Is it safe?
Is it reliable?
Where are my data?
How toIntegrate?
How to support my SLA?
Is it compliant?
Vendor lock-in?
Cloud Reference Architecture
16
Source: NIST Cloud Computing Reference Architecture
Statement
I'm pushing my organization
17
organization towards the cloud
Agenda
• Cloud Computing
• My view on Enterprise Architecture
• What is going on?
• What is the relationship between Cloud Computing and EA?
18
Computing and EA?
DYA®
StrategicDialogue
NewDevelopments
Developmentwith
Businesssolutions
Developmentwithout
Architecture
Business solutions
Governance
19
DYAprocesses
Dialoguewith
Architecture
Architectural
Services
Dynamic ArchitectureBusiness
architectureInformationarchitecture
Technicalarchitecture
Instruments
Strategic
NewDevelopments
DevelopmentBusinesssolutions
Developmentwithout
Architecture
Business solutions
Governance Managementletter
Business case
Project-proposal
Project-start-architecture
20
DYAprocesses
StrategicDialogue
DevelopmentsDevelopment
withArchitecture
solutions
Architectural
Services
Dynamic ArchitectureBusiness
architectureInformationarchitecture
Technicalarchitecture
BuildingPermit
Architecture-framework
architecture
Main principles DYA®
• The architecture process is as important as the architecture products
• Architecture is an ongoing process
• Architecture facilitates change
• Just enough, just in time architecture
21
• Just enough, just in time architecture
• Deviations from the architecture are allowed, but in a controlled way
Architectures
BusinessArchitecture
InformationArchitecture
TechnicalArchitecture
Enterprise
Depth ofArchitecture
Breadth of Architecture
Enterprise or Strategic ArchitectureCityplan
22
Portfolio, Domain
Project, SolutionProject or Solution Architecture
Business Domains IT Domains
Domain or Segment or Portfolio Architecture
Agenda
• Cloud Computing
• My view on Enterprise Architecture
• What is going on?
• What is the relationship between Cloud Computing and EA?
23
Computing and EA?
What are the top-3 issues when
implementing Salesforce?
1. CRM-process design
2. Organisational change
3. Contractual issues
24
What’s new?
Supplier
Number of options increases
LeveranciersLeveranciers
Leveranciers
25
Business IT
LeveranciersLeveranciers
LeveranciersLeveranciers
LeveranciersLeveranciers
Supplier
Example:
Tax Office and the Government Cloud
26
GovernmentCloud
PublicClouds
PrivateCloud
What is the business doing?
27
Marco Gianotten on Twitter:
Cloud leads to chaos: business-lines just do it and
don't mind integrity or integration
28
What does it mean for IT?
29
Marco Gianotten on Twitter:
A cute cloud-shaped doormat at Van Lanschot Bankers' IT department. Isn't SaaS the biggest risk to silo IT?
What does it mean for IT?
30
Bernard Golden op Cio.com:
IT has to develop a strategy that makes it possible to accept everything from everyone
Statement
The Business should have
complete freedom
31
complete freedom in choosing their cloud services
Issues
• Number of sourcing options increases− Cloud is like a candy store
• Cloud has a huge impact on integration and coherence ���� Revival of best-of-breed?− Without architecture it will become a mess
32
− In the past point solutions were inside the organisation, now they are outslide. Point solutions inside the organisation can be connected to a bus, outside they cannot (yet)
• IT-manager (CIO) is responsible for integration, but not for the purchases of the business− Businesses purchases solutions (SaaS) indepedent from IT
Agenda
• Cloud Computing
• My view on Enterprise Architecture
• What is going on?
• What is the relationship between Cloud Computing and EA?
33
Computing and EA?
Cloud and Architecture?
AgilityWith Architecture
34
Adoption of Cloud over time
Without Architecture
Source: Seize the Cloud, Sogeti
Cloud and Architecture?
Costs
WithoutArchitecture
35
Adoption of Cloud over time
With Architecture
Source: Seize the Cloud, Sogeti
Supplier
Demand and supply of services
LeveranciersLeveranciers
Leveranciers
36
Business IT
LeveranciersLeveranciers
LeveranciersLeveranciers
LeveranciersLeveranciers
Supplier
Funnelinternaldemand
Inte-grate
internalsupply
Manageand
Publishservices
Inte-grate
externalsupply
Funnelexternaldemand
Requirements architecture
• More important to:− Differentiate (business function / capability)
− Make distinction between function and construction
− Standardize
− Put emphasis on interoperability and decoupling
37
− Find opportunities and offer solutions
− Have knowledge of business domain
• Less important to:− Work on (conditions for) constructions
What architectures and for what?
Party Aspect Type of architecture
Consumercloud services
Demand for services Required services (per business function) � target
service portfolio
Procurement and integration of services
StandardsPrinciplesPolicies
38
Policies
Migration to cloud services
Blueprints for transformationprojects
Provider cloud services
Supply of services Available services � baseline
service portfolio
Procurement and integration of public cloud services
StandardsPrinciplesPolicies
Build the cloud Blueprint technical infrastructure
Example Policies
39
Source: http://cloud.sogeti.nl/Presentaties.aspx
Example Principles
Process
1. SaaS selection, approval and implementation process must follow the ‘normal’ procedure including EAB approval.
2. SaaS solutions must always be taken into account in software selection processes.
3. SaaS vendor dependency must be well managed, especially in case of very business specific ‘niche’ applications, provided by only a few niche vendors
Information Application Technology
Governance
40
1. Prime SaaS candidates:- Outsourced bus. processes
- Stand-alone & standard business processes
2. No preclusion of SaaSsolution candidates based on business process area
3. Business Process Architect must assess risks & approve in all other cases.- BIA (Business Impact
Assessment) required; (segregation in multi-tenant offerings; Identity management federation)
1. Prime SaaS candidates:- Limited information exchange
with SaaS domain; (to be evaluated from a business process perspective).
2. SaaS candidates dealing with sensitive/ privacy information must be checked against internal and external regulations (Philips Classification, SOX, HIIPA, etc.) :- PIA (Privacy Impact
Assessment) required
3. Information architect must approve.
1. Prime SaaS candidates:- Loosely coupled applications
(decision by the architects)
- No solution planned (8Q RM).
2. SaaS candidates to be tightly integrated with other IT building blocks (both SaaS and non-SaaS) must be checked on:- No short term alternative
- ‘Decoupling hub’ at Philips side taken into account
- BIA Assessment required
3. Application architects must assess risk and approve
1. Prime SaaS candidates:- Commodity IT-Solutions
- Via existing providers.
2. SaaS candidates based on differentiating techno-logy solutions need to be assessed on:- Integration & compatibility
between Philips and SaaSTechnology Infrastructure.
- Integration with Philips security and identity & access management Infrastructure:
SSO & User mgt. federation is key requirement
3. Technology architect must assess risk & approve.
Process Information Application Technology
Source: http://cloud.sogeti.nl/Presentaties.aspx
Conclusion
• EA is a must, also with Cloud Computing
• Cloud Computing does not lead to completely new types of EA artefacts but….
− More distinction between function(demand) and construction (supply)
− More important to start thinking from a business architecture perspective
− Decoupling point can shift
41
− Decoupling point can shift
− Be aware that Cloud will lead to different business models
• Way of doing EA will change
− Not by means of rules and guidelines (to limit choices / design freedom) but by means of guiding principles, services and solutions (to provide choices / alternatives)
− EA has to move to the front end of decision making processes
42
Local touch - Global reach
Additional Statements
Statement
Cloud Computing is old wine in new
44
is old wine in new bottles
Statement
In 3 years time architects have to clean up the mess
45
clean up the mess cloud computing has left behind