Service Oriented Architecture Introduction

Andriy Budayhttp://andriybuday.blogspot.com/

2

What is SOA?

SOA is for a Business

Why do we need SOA?

Advantages

Services

Building blocks

Architecture concepts

Our way to success with SOA

Further research and discussion

Agenda

3

SOA is an architectural style of building software applications that promotes loose coupling between components for their reuse.

What is SOA?

4

A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.

SOA wikipedia definition

5

Analyze your BusinessASBASB BLTBLT

HDLHDL

AFTAFT TGITGI FRYFRY

DRWDRWSWGSWG

QYDQYD DLYDLY

BSTBST

WIUWIU

ASBASB

ZISZISXOIXOI CUICUI

RMORMO

DLYDLYXPSXPS

KYFKYF

KFCKFC

WHRWHR

JIAJIA GEXGEX

FQAFQAVUHVUH

HCOHCO

WKDWKD

ECPECP

SKDSKD

MFPMFP

WCPWCP

DKEDKEAJTAJT

6

Identify Business Areas

ASBASB BLTBLT

HDLHDL

AFTAFT TGITGI FRYFRY

DRWDRWSWGSWG

QYDQYD DLYDLY

BSTBST

WIUWIU

ASBASB

ZISZISXOIXOI CUICUI

RMORMO

DLYDLYXPSXPS

KYFKYF

KFCKFC

WHRWHR

JIAJIA GEXGEX

FQAFQAVUHVUH

HCOHCO

WKDWKD

ECPECP

SKDSKD

MFPMFP

WCPWCP

DKEDKEAJTAJT

COP

Navigation

Protectors

Alerts

7

Mapping to Software

"Network"

COPCOPCOPCOP

Nav.Nav.Nav.Nav.

AlertsAlertsAlertsAlerts

Prot.Prot.Prot.Prot.

8

What are advantages?

9

Software reuse

Productivity increases

Increased agility

Advantages of service-oriented development

10

Better alignment with the business

A better way to sell architecture to the business

Advantages of an SOA strategy

11

Self-contained module that performs a predetermined task

Software components that have published contracts/interfaces

Black-box to the consumers

Platform-Independent

Language-Independent

Operating-System-Independent

Interoperable

What is Service

12

Why do we need SOA?

13

Why do we need SOA?

14

Common Understanding

15

Loose coupling - Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other

Service contract - Services adhere to a communications agreement, as defined collectively by one or more service description documents

Service abstraction - Beyond what is described in the service contract, services hide logic from the outside world

SOA Architectural Concepts

16

Service reusability - Logic is divided into services with the intention of promoting reuse

Service composability - Collections of services can be coordinated and assembled to form composite services

Service autonomy – Services have control over the logic they encapsulate

SOA Architectural Concepts

17

Service optimization – All else equal, high-quality services are generally considered preferable to low-quality ones

Service discoverability - Services are designed to be outwardly descriptive so that they can be found and assessed via available discovery mechanisms

SOA Architectural Concepts

18

Could be Web Services (XML, SOAP, WSDL, UDDI)

SOAP, RPC

REST

DCOM

CORBA

DDS

WCF

Whatever you like

Realizing SOA

19

How to success in SOA journey?

20

SOA = Architecture

Start Small

Grow Organically

Exploit Business Knowledge

Evangelize

Govern

Measure

SOA strategy to succeed

21

Create a Strong Service Catalog

Communicate Your Service Catalog

Start Simple

Common Practice

Best Practice

Be Standards Based. Be Smart

Abstract Complexity

Remember Human Element

Technical execution

2222

Ask your questions!

23

My article:

http://andriybuday.blogspot.com/2010/04/service-oriented-architecture.html

Links:http://www.cio.com/article/40941/SOA_Definition_and_Solutions

http://elementallinks.typepad.com/bmichelson/2005/11/infoworld_soa_e.html

http://www.gartner.com/it/content/754400/754413/twelve_common_soa_mistakes.pdf

http://www.soapatterns.org/masterlist_c.php#ch11

Where to go from here?