SERVICE ORIENTED

ARCHITECTURE
17CS14802
 INTRODUCTION
• Define Service
• Service -> It is a logical encapsulation of self
contained business functionality.
• Hotel and services
• three logical departments / services to work together
- counter, kitchen and waiter
 Business service
• Definition:
• Business service: – It’s a logical encapsulation of
self contained business functionality.
 Order system

• For Ex; figure ‘order system’ shows a simple ordering

system which is achieved by different services like payment
gateway, stock system and delivery system coming together.
 Fundamental of SOA
• A service oriented represents a distinct
approach for separating concerns.
• What this means is that logic required to
solve a large problem can be better
constructed through decomposition into
collection of smaller related pieces.
A service-oriented analogy(similarity)
 Service Encapsulation
• Services encapsulate logic within a distinct context.
(situation)
• This context is directly related to a business task, business
entity, or other logical grouping.
• Service task can be small or large.
• Service logic can encompass the logic provided by other
services.
• Services can be composed to produce other services.
Business processes drive the design.
• Services execute in predefined sequences that match
business logic and runtime conditions.
Service Encapsulation
 How Services Relate
• In SOA, services can be used by other services or other
programs.
• The relationship between services is based on an
understanding that for services to interact, they must be
aware of each other.
• Awareness is achieved through the use of service descriptions.
(Description: name, location, data exchange requirements)
• Services are loosely coupled through service descriptions.
• For example, Figure illustrates that service A is aware of
service B because service A is in possession of service B's
service description
How Services Relate
 How services communicate
• Services need to cooperate with other
services and so they must communicate .The
communication framework is called as
messaging.
• Messages, like services, are autonomous.
• After a message is sent, the service loses
control of what happens to the message.
• Messages carry enough intelligence to self-
govern their parts of processing logic
How services communicate
 How services communicate
• Services that provide service descriptions and
communicate via messages form a basic
architecture.
• Three core components (services,
descriptions, and messages) distinguish
distributed System from Service Oriented.
 Service-oriented architecture
• To define loosely coupled and interoperable
services/applications and to define a process for
integrating these interoperable components.
• Applications within a SOA are composed dynamically
from the deployed and available services in the
network.
• Services are dynamically discovered and bound
together in a loosely coupled manner.
• Dynamic construction allows the system to quickly
respond to new business requirements.
 Service-oriented architecture
• Services provide increased stability and
availability to users, reacting to component failure
by finding and binding to equivalent components
without requiring human intervention.
• Web and Web Services – come under SOA.
• In Web, message exchange is done using HTML,
adequate for common user interaction.
• For more complex business model, WSA extends
interaction pattern further by adding XML.
Message interaction pattern
 SOA - Steps in interaction pattern
1. Service provider - creates a service for interaction -
exposes the service’s description for consumers with
the necessary message format + transport bindings.
2. Registry - The service provider register this service
and its description with a registry of choice.
3. Service consumer - discover service – from
registry /directly from service provider and start
sending messages (well-defined XML format) that
both the consumer and service can consume.
SOA - Steps in interaction pattern
 The roots of SOA
(comparing SOA to past architectures)
What is architecture?
• The standardized definition was abstract in
nature, but specifically explained the
technology, boundaries, rules, limitations, and
design characteristics that apply to all
solutions based on this template.
 Types of Architectures
1. Application architecture
2. Enterprise architecture
3. Service-oriented architecture
 Application architecture
• blueprint - to an application development team -
team of construction workers.
• Different organizations document different levels of
application architecture.
• Some keep it high-level, providing abstract physical
and logical representations of the technical
blueprint.
• Others include more detail, such as common data
models, communication flow diagrams, application-
wide security requirements, and aspects of
infrastructure
 Application architecture
• It is not uncommon for an organization to have
several application architectures.
• A single architecture document typically represents a
distinct solution environment. For example, an
organization that houses both .NET and J2EE
solutions would very likely have separate application
architecture specifications for each.
• A key part of any application-level architecture is
that it reflects immediate solution requirements, as
well as long-term, strategic IT goals.
 Enterprise architecture
• In larger IT environments, the need to control and
direct IT infrastructure is critical.
• When numerous, disparate application
architectures co-exist and sometimes even
integrate, the demands on the underlying hosting
platforms can be complex.
• It provides a high-level overview of all forms of
heterogeneity that exist within an enterprise, as
well as a definition of the supporting
infrastructure.
 Enterprise architecture
• Changes to enterprise architectures directly
affect application architectures, which is why
architecture specifications often are
maintained by the same group of individuals.
• Enterprise architectures often contain a long-
term vision of how the organization plans to
evolve its technology and environments.
 Service-Oriented Architecture
• Service-oriented architecture spans both
enterprise and application architecture
domains.
• SOA applied across multiple solution
environments
• SOA supports reusable and interoperable
services based on a vendor-neutral
communications platform.
• does not mean that the entire enterprise must
become service-oriented.