0% found this document useful (0 votes)
27 views26 pages

Chapter 3 Service Oriented Architectures

The document discusses service oriented architecture (SOA). It defines SOA and its key components and principles, including loose coupling and service contracts. The document outlines the business benefits of SOA such as decreased costs, increased agility, and technical benefits like scalability. It also covers drivers of SOA, how to implement SOA, and when not to use SOA.

Uploaded by

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

Chapter 3 Service Oriented Architectures

The document discusses service oriented architecture (SOA). It defines SOA and its key components and principles, including loose coupling and service contracts. The document outlines the business benefits of SOA such as decreased costs, increased agility, and technical benefits like scalability. It also covers drivers of SOA, how to implement SOA, and when not to use SOA.

Uploaded by

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

Selected Topics in

Computer Science
Chapter 3 Service Oriented
Architecture
Agend
a
What is it?
Why to use it?
When to use
it?
How to implement it ?
Where not to apply it?

2
Service oriented
Architecture

3
What is (Software) Architecture?
⚫ Software architecture is the fundamental organization
of a system, embodied in its components, their
relationships to each other and the environment, and
the principles governing its design and evolution.
- IEEE 1471-
2000

4
What is Service ?
⚫ A mechanism to enable access to one or
more capabilities
⚫ using a prescribed interface
⚫ consistent with constraints and policies as specified
by the service description.
⚫ Windows service : RPC Locator, Event Log
⚫ Software Service: Distribution, Alert, Log

5
So SOA is :
⚫ A business-centric IT architectural approach
that supports integrating your business as
linked, repeatable business tasks, or services.
- IBM
⚫ Service Oriented Architecture is a paradigm for
organizing and utilizing distributed capabilities
that may be under the control of different
ownership domains.

6
Components of SOA
Ref: Element
of SOA SOA

Service
Front Service Service Bus
Repository
End

Contract Implementation Interface

Business Logic Data

7
Architectural Principles
⚫Loose coupling - Services maintain a
relationship that minimizes dependencies and
only 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
⚫Service reusability - Logic is divided into
services with the intention of promoting reuse
8
Architectural Principles…
⚫Service composability - Collections of services
can be coordinated and assembled to form
composite services
⚫Service autonomy – Services have control over
the logic they encapsulate
⚫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 9
Service oriented
Architecture

10
Business Benefits
⚫ Decreased cost:
⚫ Add value to core investments by leveraging existing
assets
⚫ New systems can be built faster for less money
because
⚫ Reducing integration expense
⚫ Built for flexibility
⚫ Long term value of interoperability

11
Business Benefits…
⚫ Increased employee productivity:
⚫ Built on existing skills
⚫ Consolidate Duplicate Functionality
⚫ Built for partnerships:
⚫ Standards based
⚫ Business relationships expressed via service
interactions
⚫ Integration is driven by what is needed, not
what is technically possible

12
Business Benefits…
⚫ Agility - Built for change
⚫ Helps applications evolve over time and last
⚫ Abstract the backend and replace over time
⚫ Focusing on core-competencies
⚫ Incremental implementation approach is supported.
⚫ Service Outsourcing – new business model!

13
Technical Benefits
⚫ Services Scale
⚫ Build scalable, evolvable systems
⚫ Scale down to mobile devices
⚫ Scale up to for large systems or across
organizations
⚫ Manage complex systems
⚫ Does not require centralized services
⚫ Empowers users with high end communication
⚫ Platform independent Use
⚫ Loose Coupling allows flexibility
14
Service Oriented Architecture

15
Driver
s⚫Large scale Enterprise systems
⚫ Internet scale provisioning of services
⚫ Reduce the cost of doing business
⚫ Implementation abstraction
⚫ Business process reuse (multiple use cases
for same process)

16
Service oriented
Architecture

17
Getting to SOA
⚫ Think services not objects
⚫ Select which services to expose
⚫ Choose a communication
mechanism
⚫ Consider the Security mechanism
⚫ Consider the re-usability

18
Comprises of
⚫ Services : a function or business processing that is
well-defined, self-contained, and does not depend
on the context or state of other services
⚫ Loan Processing Service, Weather Forecast Service
⚫ Connections : The link connecting these self-
contained distributed services with each
other.
⚫ For web services : HTTP and SOAP.

19
Service
Request - Response Service
Directory/

Register The Query For


Repositor Service
Service
y
Service Service
Provider Consumer

Invoke Service (via


Proxy)
20
Web Service Example Using
ASP.NET
<%@ WebService Language="VBScript" Class="TempConvert" %>

Imports System
Imports System.Web.Services

Public Class TempConvert :Inherits WebService


<WebMethod()>
Public Function FahrenheitToCelsius (ByVal Fahrenheit As String) As String dim
fahr
fahr=trim(replace(Fahrenheit,",","."))
if fahr="" or IsNumeric(fahr)=false then return "Error"
return ((((fahr) - 32) / 9) * 5)
end function

<WebMethod()>
Public Function CelsiusToFahrenheit (ByVal Celsius As String) As String dim
cel
cel=trim(replace(Celsius,",","."))
if cel="" or IsNumeric(cel)=false then return "Error"
return ((((cel) * 9) / 5) + 32)
end function
end class
21
Web Service Example Using
ASP.NET
⚫ Test the Web service :
⚫ Celsius To Fahrenheit
⚫ Fahrenheit To Celsius
⚫ Remember :
⚫ SOA != Web service.
⚫ Web services can implement a service-
oriented architecture.

22
Challenges
⚫ Managing services
⚫ Insufficient attention to governance of services can
cause performance and reliability issues
⚫ Providing proper security for roles
⚫ Assuring inter-operability of Services

23
Service Oriented Architecture

24
Where Not to use SOA?
⚫ When you have homogenous IT
environment
⚫ When real time performance is critical
⚫ When tight coupling is a pro not a con
⚫ When things don’t change

25
Service
Question - Answer

Question/
Request

Presente Audienc
r e

Answer/
Response
26

You might also like