int-3: realistic service oriented architecture approaches michael boyd & bernard bresser...

INT-3: Realistic Service Oriented Architecture Approaches

Michael Boyd & Bernard BresserProgress Software

How to begin implementing aService Oriented Architecture (SOA),

one step at a time

Realistic SOA Approaches

What you will learn today

© 2007 Progress Software Corporation3 INT-3: Realistic Service Oriented Architecture Approaches

Agenda

The SOA starting point What you will need

• A tale of two architectures

• Process, process, process

• Think strategically, act locally

Common pitfalls First steps when you get back home

Realistic Service Oriented Architecture Approaches


Introducing SOA & SOBA

An approach for building agile and flexible business applications• Loosely coupled services

= flexible business processes

SOA is not A product or application A specific technology A specific standard A specific set of rules

Service-Oriented Architecture > Service-Oriented Business Applications


Optimization

Transformation

Responsiveness

Functionality

Cost Effectiveness

Initial Services

Architected Services

MeasuredBusiness Services

OptimizedBusinessServices

BusinessServices

CollaborativeServices

The SOA Maturity Model

The Impact of SOA


SOA In Summary

SOA• The architecture for the

agile business

SOA is a design approach• Not a technology

Take small steps• Evolution, not revolution


Optimization

Transformation

Responsiveness

Functionality

Cost Effectiveness

Initial Services




BusinessServices


The SOA Maturity Model

The Impact of SOA


Agenda

The SOA starting point Starting your own evolution



• Think globally, act locally




A Tale of Two Architectures

You cannot reach the top of the SOA mountain overnight

Initial Services




BusinessServices




You will need two architectures during the transition period

This allows for small, incremental steps

New Service

Oriented Architecture

Existing Architecture



Communications is conducted point to point, synchronous and unreliable

Process logic is fragmented across applications and platforms and implemented differently in each place

Data comes in multiple incompatible formats

Communications are direct to a centralized service bus

Process logic is coherently defined in a single model which can be edited and redeployed quickly

Data comes expressed as XML

Existing Architecture New SOA (ESB)


Example: Using Two Architectures

P3P1P2

OrderMgmt Order

Fulfillment

OrderProcess

Business Applications

Finance

SupplierMgmt

CRM

TrackingService

PartnerBack Office

MFG CRM

Adapter

Adapter

Integration Broker

Enterprise Service Bus (ESB)

New SOA (ESB)Existing Architecture

Adapter


Process, Process, Process

“Trying to extract business functions from larger applications is like trying

to extract bricks from a large wall. It's possible, but not simple. ”

Gartner – September 2005



To move faster to meet the market, you cannot just code your way out of it –

you must change your processes Success is using “just enough process”

(CMMi Level 3-ish…)It never means “use no process”

Expect that development styles will change as SOA implementations begin



Combination of steps that allow you to meet your

business’ needs every time

What is the Best Process?



Moving to SOA requires developers to:• Specify contracts and interfaces

• Harvest existing systems for logic

• Wrap legacy systems

• Define system monitoring and management

• Specify service policies & granularity– How small / big is a service ?– You don’t want 74 similar ones !

SODA - Service Oriented Development of Applications


Process: Contracts and Interfaces

Input from calling serviceData format and type (or what’s the XML Schema)Service functionality options (or actions or events)Details on business process flow (i.e. UML graphic)

Output from Service:•Data result from service events•Error status or results from service

Other Details:▼Service Owner▼Service Design▼Service History▼Service Cross-Ref


Process: Harvesting Existing Logic

• Guideline how to approach assessment, analyses, redesign, harvest, build and test…

• …NOT the enforced way how to get there!

• Break the larger project into manageable smaller iterations to mitigate risk

• Search on “Transform” in PSDN

Awareness TransformationAssessment

Analysis & Modeling

Redesign & Harvest Build & Test Transformation

Continues…

Engagement

Capability Gap Fulfillment

Project Planning & Management

Commitment

Application Transformation Approach


Strategic SOADefine your long-term SOA vision

Think Globally, Act Locally

Succeed by thinking

strategically but acting tactically

Tactical SOAImplement first

elements of your SOA vision on next

business-based project

Add SOA elements into each successive

business-based project until SOA is

realized


Think Globally – Strategic SOA

Get executive commitment to an overall SOA strategy

The Key reason for SOA is Business Agility• Code reuse is just a means to get there

If possible, get funding for some overall SOA infrastructure needs• Resource Management – roles & duties• Developer training• Cross-application tools

Set expectations of evolving process

In order to be agile, businesses need disposable business rules –

ones that are cheap and easy enough to throwaway and replace as business changes.

- Ronald Ross, Business Rule Concepts“Father of Business Rules”


Think Globally – Strategic SOA

Get executive commitment to an overall SOA strategy

The Key reason for SOA is Business Agility• Code reuse is just a means to get there

If possible, get funding for some overall SOA infrastructure needs• Resource Management – roles & duties• Developer training• Cross-application tools

Set expectations of evolving process


Act Locally – Tactical SOA

Find high-value business project• Loosely coupled business processes

• Can benefit from Business Process Changes

• Has high-value to the business

Build new SOA and funding into project plan• Architect in minimum SOA

• Include new processes– Service Granularity– Service Contracts


P3P1P2

OrderMgmt Order

Fulfillment

OrderProcess


Finance

SupplierMgmt

CRM

TrackingService

PartnerBack Office

MFG CRM

Adapter

Adapter

Integration Broker



Adapter

Act Locally – Tactical SOA: the First Project


Act Locally – Tactical SOA

SOA implemented• Refine architectural gaps

– Context and Security are most common– Service Granularity– External Service Interfaces

• Project Retrospective– Look for process improvements

Repeat on next high-value business project• Consider as an “SOA Tax” on development


P3P1P2

OrderMgmt Order

Fulfillment

OrderProcess


Finance

SupplierMgmt

CRM

TrackingService

PartnerBack Office

MFG CRM

Adapter

Adapter

Integration Broker



Adapter

Act Locally – Tactical SOA: Additional Projects

Adapter

Adapter



Agenda








Common Pitfalls: Communication

Communicate the Vision• Actively sell to the business the agility values of

an SOA approach & benefits of the change• Keep the SOA Vision simple• Full team – business, development (IT), and

users.

Communicate the Technical Reality• Initial prototypes include experimenting

It’s more about people than technology


Common Pitfalls: Process

“We only have three people, we don’t need process – we just talk about it…”• But is this still possible when you open to

external services?

Is this what you are thinking…?



“But I don’t need SOA now…”• But when will the business change?

– Mergers & Acquisitions– Competitive Challenges– Faster time to market– Respond faster to change

Is this what you are thinking…?



Is “Just Enough Process” still ok?• Rigid enforcement of process!

– If you are lax, problems will overwhelm you– Better to identify problems and fix process

Clear Roles & Responsibilities Training on new approaches

• Modeling business processes

• Documenting service contracts

Coordinating your development work



Practice new approaches• Utilize the OERA

• Separation of Business Logic

• Gain experience with new tools

• Understand the standards:– Technical: Web Standards, JMS– Industry: How does your domain share data?

Coordinating your development work


• Guideline how to (re-)architect a modern application..

• ..NOT the enforced or only way to do it!

• Prioritize! Maybe you need n-tier or integration first before separating ALL the layers, all the clients, all data access, etc!

Provides a structured and planned to a new architecture

PresentationPresentation

Business ServicesBusiness Services

Data AccessData Access

Data SourcesData Sources

Co

mm

on

Infra

stru

ctu

reC

om

mo

n In

fras

truc

ture

Enterprise ServicesEnterprise Services


OpenEdge® Reference Architecture


Common Pitfalls: First SOA Projects

Business Project Qualification• Ensure there is an immediate business ROI

– Can this help us grow revenue?– Reduce expenses?– Improve efficiency?

Technical Qualification• Define Integration solution for problem

Service and Event Reuse Potential• Simplify follow-on projects with common

services and infrastructure

Focus on the quick success


Agenda








Realistic SOA Approaches

A SOA strategy is incremental and progressive• Follow the maturity model and have clear,

realistic objectives

Be Strategic AND Tactical• Set your Vision and Implement in Steps

Success Factors

Steps to Success Define a SOA Vision to achieve business agility

Determine where you are in the SOA Maturity Model and key goals and key practices to achieve the next level

Use high-value business projects for your first steps

Build and refine “just enough process” for your needs


For More Information, go to…

PSDN• A New Service-Oriented Architecture (SOA) Maturity Model • Principles of a Service-Oriented Architecture• Fundamentals of Service–Oriented Architecture• Service-Oriented Architecture: Overview and Business Drivers • Design Best Practices: Methodology using Patterns • SOA Worst Practices, Volume 1• Expertise Centers: SOBA & SOA Infrastructure• OpenEdge® Evaluation Kit and Product Tour

Progress eLearning Community:• SOA Essentials for OpenEdge Developers• SOAP for OpenEdge Developers• What's New in OpenEdge 10.1: SOA Support • Service Oriented Integration with Sonic ESB® 7.0


Relevant Exchange Sessions

Already held (go back and review): INT-1: Achieving SOA: The Product Solution SONIC-2: Enterprise SOA Implementation: What Your Mother

Failed to Tell You

Still to come: INT-4: Introducing Sonic ESB SONIC-5: Global Approach to SOA Enabled by Sonic ESB ARCH-7: A Class-based Implementation of the OERA SONIC-8: Extend your ESB with SOA Management INT-11: It’s Monday Morning, Do You Know Where Your Service

Has Been? ARCH-13: Transactions in a SOA World


Questions?


Thank you foryour time

int-3: realistic service oriented architecture approaches michael boyd & bernard bresser...

Documents

summarysoathe architecture

progress software corporation

needa tale

evolutiona tale

agile businesssoa

nota product

design approachnot

incremental stepsint