Soa 101

31
SOA 101 David S. Linthicum

Transcript of Soa 101

Page 1: Soa 101

SOA 101

David S. Linthicum

Page 2: Soa 101

• Blogs:– eBizq.net “Linthicum Channel”– IT Toolbox “CEO’s Guide to SOA and Application

Integration”– InfoWorld “Real World SOA”

• Weekly Podcast– www.soaexpertpodcast.com

• New Gig– CEO BRIDGEWERX

• New Book: 12 Steps to SOA

Page 3: Soa 101

SOA…What’s New Here?

Page 4: Soa 101

The Integration Challenge…

The N-squared Integration Problem:

Source: Copyright © 2002 ZapThink, LLC

ContentManagement

Web Site

File System

RDBMS

Office Documents

B2B Exchanges

Directory

ERP / CRMSystems

Mainframe / Legacy

NetworkedDevices

No

N- o

r S

EM

I-S

TR

UC

TU

RE

DS

TR

UC

TU

RE

D

Page 5: Soa 101

…Made Worse by External Integration

• 70% of IT development budgets are spent on integrating different systems – ZapThink

Source: Copyright © 2002 ZapThink, LLC

ContentManagement

Web Site

File System

RDBMS

Office Documents

B2B Exchanges

Directory

ERP / CRMSystems

Mainframe / Legacy

NetworkedDevices

No

N- o

r S

EM

I-S

TR

UC

TU

RE

D

STR

UC

TU

RE

D

Source: Copyright © 2002 ZapThink, LLC

ContentManagement

Web Site

File System

RDBMS

Office Documents

B2B Exchanges

Directory

ERP / CRMSystems

Mainframe / Legacy

NetworkedDevices

No

N- o

r S

EM

I-S

TR

UC

TU

RE

D

STR

UC

TU

RE

D

Page 6: Soa 101

The “Rat’s Nest” Architecture

FBT PAY GNTS

TRDS

Client

Customs

RREIPS Integrated A/C Refunds

RBADef

PaymentsExcise

CR

PKI

ECI ADD AWA ELS

Client Staff RemoteStaff

TAXAGENTS

GCI

Call Centers

WOC

CCD

TASS

StaffPhone

ComplianceStaff

BOA

Ref material

Bus. Intel

NTS A/c

BEP

CDCCCWMS

BANK

DDDR

1

Data…….

Penalty

Business

IVR

1

Page 7: Soa 101

IT: Fulfilling Business Requirements

Business Requirements• Service Customers• Manage Operations• Increase Worker Productivity• Communicate with market• Ensure reliable and secure

operations• Develop new products and

services• Respond to new business

drivers

IT Capabilities• Implement CRM Systems• Implement ERP Systems• Manage desktop environments• Manage server environments• Manage email systems and web

sites• Manage network and storage

operations• Develop applications

Page 8: Soa 101

However, it rarely works that way…

?Final Im

plementation

Long development

cycleIT

Interpretation

Business Requirements

• Requirements change

• Interpretations often inaccurate or limited

• Lengthy development cycles impervious to change

• Implementations “cast in concrete”

Result: IT that places Result: IT that places limitations on Businesslimitations on Business

Page 9: Soa 101

What is a Service-Oriented Architecture?

• Access software via Services that are easy to find and connect to

• Web Services provide a standard way of building and accessing Services

• Developers & integrators can build applications out of Services

Page 10: Soa 101

Application Integration Solution Types

Page 11: Soa 101

The High Level Integration Stack

Page 12: Soa 101

Logic

Transformation Formatting

Data

Logic

User Interface

Data

Page 13: Soa 101
Page 14: Soa 101

Service Oriented Application Integration

• Service integration to create a composite application

• Sharing business logic

• Sharing code

• Sharing processing– Shared programs– Shared transactions– Shared objects

Page 15: Soa 101

Application Integration is Evolving

Business Process Control (Process Integration Oriented)

Page 16: Soa 101

Contrasting Three Forms of Integration

Data Consistency Multi-step Process Service Oriented Loosely coupled integration Multiple applications Asynchronous dominates One-way Simple abstraction of

business rules

Loosely coupled integration Multiple applications Can be either

Asynchronous or Synchronous based

One-way and request/reply Limited complexity in

abstraction of business rules

Loosely or tightly coupled integration

Single application Synchronous dominates Request/reply Complex abstraction of

business rules

Page 17: Soa 101

Multistep Process (Information-Oriented) Dominates… For Now

Page 18: Soa 101

Process Orchestration will Control SOA

Page 19: Soa 101

Composite Application

Page 20: Soa 101

Value of Services

• Limitations of information-oriented integration– Limited visibility– Limited reuse– Latency

• Advantages of leveraging service-oriented integration– Visibility at the information and the behavior levels– Reuse of services among trading partners– Real-time integration

Page 21: Soa 101

The Economics of Integration

Initial Costs Customization ChangesMaintenance

Custom Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

The Relative Costs of Different Integration Approaches

Page 22: Soa 101

The Economics of Integration

Initial Costs Customization ChangesMaintenance

Custom Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

The Relative Costs of Different Integration Approaches

Traditional EAI, B2Bi

Page 23: Soa 101

The Economics of Integration

Initial Costs Customization ChangesMaintenance

Custom Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

The Relative Costs of Different Integration Approaches

Traditional EAI, B2BiWeb Services "Adapters"

Page 24: Soa 101

The Economics of Integration

Initial Costs Customization ChangesMaintenance

Custom Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

The Relative Costs of Different Integration Approaches

Traditional EAI, B2BiWeb Services "Adapters"Service-Oriented Integration

Page 25: Soa 101

The Economics of Integration

Initial Costs Customization ChangesMaintenance

Custom Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

The Relative Costs of Different Integration Approaches

Traditional EAI, B2BiWeb Services "Adapters"Service-Oriented Integration

Page 26: Soa 101

Development model for SOA

•Integration tightly couples end-points•Interoperability considers each end point separately

– Producer: Provides service

– Consumer: Consumes the service

•Producer/Consumers describe their interfaces and are then connected at run time (late binding)

•Focus on agreement of business service interface– Do not focus on operating system, implementation, etc….

Producer ConsumerSOA

(SharedServices)

Consumer

Interface

Producer

Interface

Page 27: Soa 101

Application Domain Integration

Domain

Data Domain Point of Access

Domain

Business ArchitectureBusiness ArchitectureBusiness Architecture

Patterns

Business Relationship Grid

Bricks

Business Processes, Styles

System Management Domain

Security Domain

Infrastructure Domain

InformationArchitecture

Technical Architecture

Gartner’s Architecture

Page 28: Soa 101

Directions for SOA

Three Levels of Web Service Engagement

Page 29: Soa 101

Goals and Characteristics of a SOA

• Improved Adaptability and Agility– Respond to business needs in near real-time

• Functional Reusability– Eliminate the need for large scale rip and replace

• Independent Change Management– Focus on configuration rather than programming

• Interoperability instead of point-to-point integration– Loosely-coupled framework, services in network

• Orchestrate rather than integrate– Configuration rather than development to deliver business needs

Page 30: Soa 101

Business Benefits of Loosely Coupled Approach

Page 31: Soa 101

Thanks!