0% found this document useful (0 votes)
78 views14 pages

Service Oriented Architecture: Misconceptions

1) This document discusses Service Oriented Architecture (SOA), including its evolution from modular programming to introducing service concepts, advantages like improved integration and reuse, and disadvantages such as non-standardization. 2) Common misconceptions about SOA are addressed, such as the notion that using web services means having an SOA, or that SOA simplifies distributed computing. 3) The document provides an overview of SOA concepts, benefits, pitfalls, and best practices for designing SOAs.

Uploaded by

Sanjiv Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
78 views14 pages

Service Oriented Architecture: Misconceptions

1) This document discusses Service Oriented Architecture (SOA), including its evolution from modular programming to introducing service concepts, advantages like improved integration and reuse, and disadvantages such as non-standardization. 2) Common misconceptions about SOA are addressed, such as the notion that using web services means having an SOA, or that SOA simplifies distributed computing. 3) The document provides an overview of SOA concepts, benefits, pitfalls, and best practices for designing SOAs.

Uploaded by

Sanjiv Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Service Oriented Architecture

MISCONCEPTIONS
BENEFITS & PITFALLS
SANJIV KUMAR
206113020
M Tech 1st yr, CSE ,
Nationa Instit!te o" Technoo#y, Tir!chira$$ai


What this diagram is all about?

What this diagram is all about?


SOA the evolution
Mo%!ar &ro#ra''in# ()*ect (riente% A$$roach

SOA the evolution
A$$ication 1
A
C
B
A$$ication 2
A
E
D

Entity A is sa'e "or )oth the a$$ication+

Can a$$ication 2 !se entity A "ro' a$$ication 1,, -hy .-hy not,
SOA the evolution

D E B C
A
A$$ication 1
A$$ication 2

Intro%!ces Ser/ice conce$t in S(A+


Advantage

Improved integration and interoperability.

No 'o%ein# re0!ire%+

Cost re%!ce%+

Inherent reuse.

1o2ere% cost an% e""ort in )!i%in# syste'+

Incre'enta #ro2th+

Streamlined architecture and solution.

Re%!ce% s3i set re0!ire'ent+

4i#hy o$ti'i5e% a!to'ation en/iron'ent+

6est o" )ree% aternati/e+



Advantage

!" standardi#ation.

7M1 is (8y#en "or S(A+

+In/est'ent on co''!nication stan%ar%+

Organi#ational agility.

-hat yo! )!i% to%ay 2i e/o/e o/er ti'e+

A)iity to "!"i the ra$i%y chan#in# 'ar3et nee%+


Disadvantage

Building SOA li$e traditional distributed system.

I'$ro$er $artitionin# o" "!nction )o!n%ary+

+Creation o" non stan%ar%i5e% ser/ices+

Creation o" non9co'$osa)e ser/ice+

%ot understanding SOA per&ormance re'uirement.

A ot o" 'essa#e $rocessin# o/erhea%+

More ayer o" a)straction 'ore $rocessin# $o2er+

%ot understanding (eb service security+

Ser/ices are oosey co!$e%+

Messa#e e/e sec!rity+


Disadvantage

%ot starting (ith !" &oundation architecture.

1ea%s $ro)e's in inte#ration o" ser/ices+

:ata $rocessin# 0!aity #et a""ecte%+

%on standard SOA.

:esi#nin# in%e$en%enty+

Re0!ires 3no2e%#e o" atest stan%ar%+

%ot creating a transition plan+

Transition to S(A sho!% occ!r in $anne% 'anner+

Re0!ire anaysis+
!isconceptions

An application that uses (eb services is SOA.

;ase

-e) ser/ice )!i% !sin# conce$t o" S(A+

SOA is mar$eting term used to rebrand distributed


computing and (eb services.

S(A is not 'e%ia hy$e+

S(A has its o2n e8istence ha/in# stan%ar%s $rinci$es+

SOA simpli&y distributed computing.

There is %i""erence )et2een :istri)!te% co'$!tin# < S(A+

:istri)!te% co'$!tin# can )e )!i% on S(A +


!isconceptions

I& you understand (eb service you (on)t have problem in


designing SOA.

S(A %oesn=t 'ean 2e) ser/ice ony+

Re0!ires co'$rehensi/e s!)*ect 3no2e%#e+

Once you go SOA everything (ill become interoperable.

;ase+

I" yo! "oo2 a o$en stan%ar%s in S(A+

SOA is simple by nature* easy to build *automatically


interoperable.

Conce$t si'$e %esi#n %i""ic!t+

:esi#ne% )y "oo2in# r!es to )e intero$era)e+


+e&erences
+

:o!#as K+ 6arry, -e) Ser/ices an% Ser/ice9(riente%


Architect!res> the sa//y 'ana#er=s #!i%e+

Tho'as Er, Ser/ice9(riente% Architect!re> a "ie% #!i%e to


inte#ratin# 7M1 an% 2e) ser/ices+

Tho'as Er, Ser/ice9(riente% Architect!re> conce$ts,


technoo#y an% %esi#n+

htt$>..222+'icroso"t+co'.)i5ta3.so!tions.soa.o/er/ie2+'s$8

,uestions?
-han$ you.

You might also like