2006 avanade inc. all rights reserved. the avanade name and logo are registered trademarks in the us...

2006 Avanade Inc. All rights reserved. The Avanade name and logo are registered trademarks in the US and other countries.

Microsoft Architect Insight Conference 2006

Avanade Confidential – Do Not Copy, Forward, or Circulate.

David Jobling, Senior Solutions Architect, Avanade UK Ltd.

March 23rd 2006

Bullet Proof SOAs


Brief

'To many people SOA appears to be the great hope, but to many others it represents their worst nightmare.'

In this session we will look at how to address this imbalance through an approach to delivering sound, stable and robust services through which you reap rewards but at a much reduced risk. '


Contact

[email protected]

Avanade UK Ltd2nd Floor135-141 Wardour StreetLondonW1F 0UTUnited Kingdom

David JoblingSenior Solution Architect

www.avanade.com


What is an SOA

Facilitates the design of software systems that provide or consume services through published interface.A powerful, flexible programming modelA methodlogy for building software


Scope

Principles of SOA can be applied at many levelsIn code– Encapsulation

Within a distributed application– Web server, app server communications etc.

To integrate applications within an organisation– Business process orchestration

To integrate at an organisational level– Business to business, commercial services


Why SOA

Cost savings during implementation and operationAn estimated 40% of IT spending is on management and integration. Even a small saving could have an enormous impact on overall budgets

Improved business operationsAutomation of business processes with real time / near real time analysis and reaction

Improved chance of deliveryOften adopted in a phased approach

that can be done over time

Invigorate business processesNew life for legacy applications exposing re-usable services

for configuration into composite application capabilities


Prepare for Next Step

SOA is transforming the enterpriseNext step is organisation-to-organisation service orientatedCommercial services and a model to support and evolve themOnly a service orientated architecture at an enterprise level will permit you to take full advantage of this next wave


You’re Going to Fail!!!

'Through 2008, 70 percent of IT organizations will fail to

successfully select and implement an SOA strategy on the first

try (0.7 probability). These organisations must be prepared to

use software services tactically while planning for strategic

evolution of their architectures.'- Gartner, June 2005,

'Management Update: Six Missteps That

Can Result in SOA Strategy Failure'


SOA Lifecycle

Envisioning– Know your capabilities– Conceptualise your

architecture– Predict the future

Planning– Start small– Architecture– Design

Execution– Development

Stabilisation– Preparation– Execution

Analysis & Feedback– Evolve the

architecture


Envisioning – Capability Mapping

Put the business process back in the driving seatUnderstand the business processes and associated capabilitiesCreate a technology and system agnostic map of your organisation’s capabilities– Keep it simple but as complex as it needs to be– Approach the task with a goal in mind (cost reduction, system consolidation)


Envisioning – Conceptual Architecture

Overlay the capability map on top of existing systems and functionality– Identify areas of consolidation– Target systems for decommissioning– Identify systems that are scheduled for decommissioning

Identify initial required system services– Do this for the entire enterprise (beyond what may be the scope of the initial project)

– Catalogue these services – this will be the basis for management and planning of the SOA within the organisation


Envisioning – Predict the Future

Leave no stone unturnedNo idea is too far in the futureInvolve all aspects of the organisation– Business directors– Product owners– IT directors– IT operations– Business operations

Solution architects can never have too much information


Envisioning - Results

Business analysis– Business process flows– Capability maps– Methodology for deriving and analysing– Business roadmap

Conceptual architecture– Service maps– Service roadmap (matched to the business roadmap)

– SOA service catalogue– Short, medium and long term service strategy


Planning – Start Small

Carefully select a process– Consumes more than one service– Try to incorporate quick wins

Use the first process to establish the patterns and development processes– Take more time than would usually be required– Establish a pattern of working to create predictability for future projects


Planning - Architecture

Understand the business processPlan for change– Identify points of flexibility– Identify points of extensibility

Make decisions with one eye firmly fixed on the roadmap– Expect ~50% of decisions to cost slightly more for no immediate benefit

– These costs are recuperated later on by the ability to accommodate change and rapid implementation of new processes


Interface Service


Be a good consumer of services– Interface contracts will change– Isolate the interface message processing from the interface business logic

Consuming Application

Business LogicInterface

LogicMessage

Processing

Published Service

Easier to specifyEasier to architectEasier to design

Easier to buildEasier to testEasier to deploy / re-deploy



Be a good provider of services– Don’t build in functionality you don’t need– Don’t be too ambitious in trying to identify re-usable

services– Enforce standards

Build for one consumer in the first instance– Promote, enhance and migrate consumers as required– Time in operation helps to decide on the specifics of an

enterprise service– Versioning is an option – needs to be balanced against

maintainability

Don’t be afraid of consistent change– Design for change to build a more agile architecture– Ultimately, react faster to business opportunities and

market changes


Planning – Detailed Design

Don’t get too hung up on designArchitecture is more importantDesign is a means to an end– Tailor the verbosity of the design to the skills and location of the developers

– Retain designs as close to the code as possible (comments)


Execution - Development

Apply service orientation at the code levelConsistency– Application architecture should define the approach to all items

– A modular service orientated sub-system is easier to write, test and maintain

– Enforce consistency though a technical framework such as Enterprise Library or ACA.NET

Standards– Establish a service authority across the organisation to review and approve application architectures and designs


Stabilisation - Preparation

Assume long term architecture– Will encounter many changes over time– Existing services and processes will need regression testing

Design for testing– May need to alter some aspects of the architecture specifically to make it easier to test and re-test

– Effort in short term but will pay off after the first change is implemented and regression testing is required

Standard architecture = standard tests– Test harnesses built around standard architectural constructs (such as interface services or data services)


Stabilisation - Execution

Aim for rapid and automated testing– Applies not just to SOAs– More expensive in short term but provides better coverage and a firm foundation for extension and expansion

Phased delivery of complete end-to-end processes– Depending on the service it may be possible to plan development and testing in such a way as to phase the implementation with complete end-to-end processes.

Isolated delivery of services– Since services are independent it is also possible to deliver into production a completed service

– Service consumer (business process) will follow later


Analysis & Feedback

Business roadmap will changeContinually identify candidates for promotion– Based on business requirements and quick wins– Feedback into development processes if the roadmap should change

Evolve the architecture– Identify points of flexibility and extensibility from experience in operation

– Don’t be afraid to undergo mass changes, design for test and build consistently to minimise impact and cost

Adopt and adapt


Design for …

Design for Change– Its going to happen

Design for Build– Alter the architecture to suit your development profiles

Design for Test– Testing must be repeatable and preferably automated

Design for Operation– Tools, tools and tools– Failure management


Questions


Avanade Assets

Avanade Quick Assessment for SOA– Takes you though business analysis– Capability mapping– Service discovery and analysis– Preparation for project engagement

ACA.NET– Application framework– Enhances (not replaces) .NET Framework– Specific tools to accelerate SOA though declarative creation of services

– Aspect oriented programming to enable consistency– Extensible framework to enable flexibility


Contact

[email protected]

Avanade UK Ltd2nd Floor135-141 Wardour StreetLondonW1F 0UTUnited Kingdom

David JoblingSenior Solution Architect

www.avanade.com

2006 avanade inc. all rights reserved. the avanade name and logo are registered trademarks in the us...

Documents

existing systems

robust services

people soa

design of software systems

system agnostic map

avanade uk

real time analysis

legacy applications