sandeep alur architect advisor microsoft...

Post on 07-Jun-2020

3 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Sandeep AlurArchitect AdvisorMicrosoft Indiasaalur@microsoft.com

Aditee ReleArchitect AdvisorMicrosoft Indiaaditeer@microsoft.com

Is SOA Dead or Alive

?

ConnotesEx

pen

sive

Big P

rojects

Momentum Continues…

Industry TrendsSOA: Service Oriented Architecture

Reuse and Agility

Web 2.0

Network Effect

SaaS: Software as a Service

Flexible pricing and delivery

RIA: Rich Internet Applications

Experience

Software + “Services”

Cloud Computing

Service Utility

Next One HourSOA & ESB – Big Buzz Words

Reality Check – Myths

Application Integration – Patterns

Reasons to go for SOATechnology Stack for SOA

Reasons to go for ESBTechnology Stack for ESB

‘Service Orientation’ – Technology Puzzle

Success Story

Demystifying SOA

Modular

Distributable

Clearly defined

Swappable

Sharable

SOA

SOA

SOA

Common Myths about SOA

1. SOA is a design philosophy independent of any product, technology or industry trend

2. SOAs may be realized via web services but using web services will not necessarily result in a SOA

3. EDI, CORBA and DCOM were conceptual examples of SOA

4. SOA is not a methodology

5. SOAs are like snowflakes – no two are the same.

6. SOA should be incremental and built on your current investments

7. SOA is a means, not an end

1. SOA is a technology

2. SOA require Web Services

3. SOA is new and revolutionary

4. SOA ensures the alignment of IT and

business

5. A SOA Reference Architecture

reduces implementation risk

6. SOA requires a complete technology

and business processes overhaul

7. We need to build a SOA

FactsMyths

Demystifying ESB

Middleware Infrastructure

Manifestation of SOA

Communication & Mediation

Connects Providers & Consumers

ESB

ESB

ESB

Common Myths about ESB

1. ESB provides EAI capabilities, but based on different architecture

2. Provides a Enterprise Messaging Layer (Not a one size fits all solution)

3. An abstract pattern that can be applied to couple an existing app server and integration middleware

4. ESB may support multiple ways of coordinating the interaction between event-driven service invocations using formal business process definitions

5. Integrated Services Environment

1. ESB is just a new name for

EAI

2. Adoption of WS-* specs

obviate the need for ESB

3. Pattern or Product

4. ESBs will be obsolete once

BPEL is widely available

5. ESBs are simply plumbing

and do not provide

sophisticated tooling

FactsMyths

Application Integration Patterns

3 Patterns of Application Integration

Style Data Consistency

Latency Scheduled toimmediate

Prevailing Interaction Style

Asynchronous, oneway

Flow Management Generally, simplescheduled batchjobs or immediatemessaging

Application Dependencies

Applications remainlogically andphysicallyindependent

1

3 Patterns of Application Integration

Style Multistep Process

Latency Scheduled to immediate

Prevailing Interaction Style

Asynchronous, one way

Flow Management

More-complex batch job streams; sophisticated orchestration usingBPM technologies

Application Dependencies

Applications remain physicallyindependent but are logically dependent from the perspectiveof completing the Process

2

3 Patterns of Application Integration

Style Composite Application

Latency Immediate

Prevailing Interaction Style

Two-way synchronous andPartially Synchronous

Flow Management

Complex interactions may be controlled by application code orusing BPM technologies orother tools

Application Dependencies

Applications are logically andphysically highly Dependent3

When to 'SOA'

Reasons to go for SOAWhen designing most large, new business applications and processes

When integrating a combination of COTS, legacy and services from other BU’s

Generalization (Service Orientation)

Use non-SOA styles for tactical applications of limited size

SOA

Technology Stack for SOA

WCF Endpoints

Windows Communication Foundation(.Net Framework 3.x)

Protocol Independence

Supports WS-*(WSE)

Host(Custom or IIS)

Consumers

SOA Reference Architecture

When to 'ESB'

Reasons to go for ESB

Multiple Communication Protocols

Intelligent Addressing, routing & Orchestration

Mediation

Complementing Application Platforms

ESB

Multiple Communication Protocols

One way Messages2 Way – Request/ResponseStore & ForwardPublish - Subscribe

Reliable MessagingExplicit Support for RESTWCFSCA

Messaging Infrastructure

HTTP/SOAP MSMQ MQ Series TCP File

Addressing, Routing & OrchestrationService Virtualization Rule Based Routing Orchestration

HTTP/SOAP MSMQ MQ Series TCP File

Line of Business Applications

Itinerary

Service Registry

Messaging Infrastructure

Mediation

Message ValidationTransformation

Protocol BindingMessage Logging & Auditing

Security

MessageX

MessageX

MessageX

Source

MessageA

MessageB

MessageC

DestinationSECURITY

Complementing Application Platforms

Load BalancingFailover

Transaction Management

Messaging Infrastructure

HTTP/SOAP MSMQ MQ Series TCP File

ESB(Guidance Kit) Technology Stack

Service Registry

Administration

Multiple Communication Protocol

Addressing

Transformation & Routing

Industry Innovations

Core FunctionsProtocols,

Transformation, Routing, Standard

Formats, Error Handling, Security,

Integration, Extensibility, High

availability & Scalability

Extended Functions

Service Life Cycle

Management

SLA Monitoring/

Management

Business Activity

Monitoring(BAM)

Complex Event

Processing(CEP)

Business Rules Engine

(BRE)

Dynamic Service

Provisioning

Graphical Editing Tools

Application Platform for 'Services'

Compose User Experience and Interaction

People using Content, BI,

Collaboration and Communication

Compose Business Process Services

Information Integration

Messaging Services

Communication Services

Standards based

Interoperability

SOA as

mechanism

to transact

SOA as

mechanism

to interact

ExposeExisting Systems

ConsumeUser Directed

Application Platform for 'Services'

Compose User Interaction

Compose Business Transaction

ExposeExisting Systems

ConsumeUser Directed

Portals, Web Parts, Smart Client,

Office Client Extensions, Mobile Client

Real Time Unified Communications,

Online P2P Offline Collaboration

Workflow, Search, Dashboards, KPIs,

Doc and Forms Libraries, Business Data Catalog

Orchestrations

Rules, BAM,

Trading Partner

Mgmt

ETL, Federated

Access, MDM

ESB, EAI, P2P,

Queues

ESB, EAI, P2P, Queues

Security

and Id

entity

Managem

ent a

nd G

overn

ance

Desig

n a

nd D

evelo

pm

ent

Application Platform for 'Services'

Compose User Interaction

Compose Business Transaction

ExposeExisting Systems

ConsumeUser Directed

SharePoint Server, .NET Compact Framework,

Silverlight,Office System, ASP.NET, Windows Client

Live Communications Server, SharePoint Server

Workflow Foundation, SharePoint Server, CAB

BizTalk

ServerSQL Server

WCF

Windows

BizTalk Server

WCF and BizTalk Server

Activ

e D

irecto

ry

Syste

m C

ente

r, Partn

ers

Visu

al S

tudio

, Patte

rns a

nd P

ractic

es, M

SF

Enterprise Service Bus (BizTalk Server 2006 R2)

AmberPoint

Application Platform for 'Services'

Case Study - 3 Tenets of Enterprise Integration

Solution Highlights

“Service Excellence Everyday”

1100 Branches, 30K User Base

18K Connected Any given time

Perception of Responsiveness

Reuse->Mainframe & Legacy Systems/Assets

.Net Smart Client with Service Integration

WinPart

Agent

WS Proxy

Local Cache

SOFAPrivate

ServicesConfig

Authentication/Authorization

Service Helpers Data Integration Orchestration

Private Services

Legacy Systems

SOFA

IFW Service

Mainframe

Data Storage

Client Tier

Security

Instru

men

tation

Co

nfigu

ration

In Summary

‘ESB’ is a manifestation of SOA

SOA is an overtly used term and forms the basis for a ‘Services’ platform

While, new architectural patterns emerge, SOA continues to fuel energy

Beginning of a new Era…

Momentum Continues…

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

top related