INT3: Realistic Service Oriented Architecture Approaches

1
INT-3 Realistic Service Oriented Architecture
Approaches
Michael Boyd Bernard Bresser
Progress Software
2
Realistic SOA Approaches
What you will learn today

• How to begin implementing aService Oriented
  Architecture (SOA),one step at a time

3
Agenda
Realistic Service Oriented Architecture Approaches

• 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

4
Introducing SOA SOBA
Service-Oriented Architecture gt Service-Oriented
Business Applications

• 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

5
The SOA Maturity Model
The Impact of SOA
Optimization
OptimizedBusinessServices
Transformation
MeasuredBusiness Services
Responsiveness
BusinessServices
CollaborativeServices
Cost Effectiveness
Architected Services
Functionality
Initial Services
6
SOA In Summary

• SOA
• The architecture for the agile business
• SOA is a design approach
• Not a technology
• Take small steps
• Evolution, not revolution

7
The SOA Maturity Model
The Impact of SOA
Optimization
OptimizedBusinessServices
Transformation
MeasuredBusiness Services
Responsiveness
BusinessServices
CollaborativeServices
Cost Effectiveness
Architected Services
Functionality
Initial Services
8
Agenda
Realistic Service Oriented Architecture Approaches

• The SOA starting point
• Starting your own evolution
• A tale of two architectures
• Process, process, process
• Think globally, act locally
• Common pitfalls
• First steps when you get back home

9
A Tale of Two Architectures
OptimizedBusinessServices
MeasuredBusiness Services
BusinessServices
CollaborativeServices
Architected Services
Initial Services
You cannot reach the top of the SOA mountain
overnight
10
A Tale of Two Architectures

• You will need two architectures during the
  transition period
• This allows for small, incremental steps

11
A Tale of Two Architectures
Existing Architecture
New SOA (ESB)

• 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

12
Example Using Two Architectures
Existing Architecture
New SOA (ESB)
SCM
Integration Broker
P1
CRM
P3
Finance
P2
Adapter
Adapter
Order Process
Order Mgmt
Supplier Mgmt
Adapter
MFG
TrackingService
Back Office
Partner
Business Applications
13
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
14
Process, Process, Process

• 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

15
Process, Process, Process
What is the Best Process?

• Combination of steps that allow you to meet
  your business needs every time

16
Process, Process, Process
SODA - Service Oriented Development of
Applications

• 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 dont want 74 similar ones !

17
Process Contracts and Interfaces

• Input from calling service
• Data format and type (or whats the XML Schema)
• Service functionality options (or actions or
  events)
• Details on business process flow (i.e. UML
  graphic)

• Other Details
• Service Owner
• Service Design
• Service History
• Service Cross-Ref

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

18
Process Harvesting Existing Logic
Application Transformation Approach

• 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

19
Think Globally, Act Locally

• Tactical SOA
• Implement first elements of your SOA vision on
  next business-based project
• Add SOA elements into each successive
  business-based project until SOA is realized

• Strategic SOA
• Define your long-term SOA vision

Succeed by thinking strategically but acting
tactically
20
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
ConceptsFather of Business Rules
21
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

22
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

23
Act Locally Tactical SOA the First Project
Existing Architecture
New SOA (ESB)
SCM
Integration Broker
P1
CRM
P3
Finance
P2
Adapter
Adapter
Order Process
Order Mgmt
Supplier Mgmt
Adapter
MFG
TrackingService
Back Office
Partner
Business Applications
24
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

25
Act Locally Tactical SOA Additional Projects
Existing Architecture
New SOA (ESB)
SCM
Integration Broker
Adapter
P1
CRM
P3
Finance
P2
Adapter
Adapter
Order Process
Order Mgmt
Supplier Mgmt
Adapter
Adapter
MFG
TrackingService
Back Office
Partner
Business Applications
26
Agenda
Realistic Service Oriented Architecture Approaches

• 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

27
Common Pitfalls Communication
Its more about people than technology

• Clear Roles Responsibilities
• Communicate the Vision
• Include full team business, development (IT),
  and users
• Keep the SOA Vision simple
• Actively sell to the business the agility values
  of an SOA approach
• Communicate the Technical Reality
• Initial prototypes include experimenting
• Over-communicate to the entire team
• Reiterate the benefits of the change

28
Common Pitfalls Process
Is this what you are thinking?

• We only have three people, we dont need process
  we just talk about it
• But how do you open to external services?

29
Common Pitfalls Process
Is this what you are thinking?

• But I dont need SOA now
• But when will the business change?
• Mergers Acquisitions
• Competitive Challenges

30
Common Pitfalls Process
Coordinating your development work

• Need Just Enough Process
• Rigid enforcement of process
• If you are lax, problems will overwhelm you
• Better to identify problems and fix process
• Clear Roles Responsibilities
• Especially Architect and Business Analyst
• Training on new approaches
• Modeling business processes
• Documenting service contracts

31
Common Pitfalls Process
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?

32
Common Pitfalls Process
OpenEdge Reference Architecture

• 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
33
Common Pitfalls First SOA Projects
Focus on the quick success

• 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

34
Agenda
Realistic Service Oriented Architecture Approaches

• 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

35
Realistic SOA Approaches
Success Factors

• 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

• 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

36
For More Information, go to

• PSDN
• A New Service-Oriented Architecture (SOA)
  Maturity Model
• Principles of a Service-Oriented Architecture
• Fundamentals of ServiceOriented 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

37
Relevant PTW / Exchange Sessions

• PTW
• Achieving SOA The Product Solution
• Transactions in a SOA World
• Implementing ESB Processes with OpenEdge and
  Sonic
• Exchange 2007
• SONIC-2 Enterprise SOA Implementation What Your
  Mother Failed to Tell You
• 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 Its Monday Morning, Do You Know Where
  Your Service Has Been?

38
Questions?
39
Thank you foryour time
40
(No Transcript)