0% found this document useful (0 votes)
18 views27 pages

Soa-Analysis & Design

The document provides an overview of Service-Oriented Architecture (SOA), detailing its characteristics, types, and the processes of service-oriented analysis and design. It outlines the objectives, goals, and steps involved in analyzing and designing services, emphasizing the differences between monolithic and microservices architectures. Additionally, it includes references for further reading on SOA concepts and design principles.

Uploaded by

deepujohre
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)
18 views27 pages

Soa-Analysis & Design

The document provides an overview of Service-Oriented Architecture (SOA), detailing its characteristics, types, and the processes of service-oriented analysis and design. It outlines the objectives, goals, and steps involved in analyzing and designing services, emphasizing the differences between monolithic and microservices architectures. Additionally, it includes references for further reading on SOA concepts and design principles.

Uploaded by

deepujohre
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/ 27

SERVICE-

ABHIJEET
KUMAR
ORIENTED
ARCHITECTURE
206124001
ANALYSIS &
DESIGN
CONTENTS

◼ What are Services?


◼ Application Architecture Models
◼ Common types of SOA
◼ Service Oriented Analysis
◼ Objectives
◼ Goals
◼ Steps
◼ Service Oriented Design
◼ Principles
◼ Objectives
◼ Goals
◼ Steps
◼ References
What are services?
SERVICES ARE COLLECTIONS OF CAPABILITIES
SOA (Service-Oriented
Aspect Monolithic Microservices
Architecture)
Single codebase, tightly Reusable, loosely coupled Fine-grained, independent
Architecture coupled modules services services

Internal function calls within the Enterprise Service Bus (ESB)


Communication app. or HTTP (SOAP/REST).
Lightweight APIs

Independent Service Fully independent


Deployment Single unit deployment
deployment deployment

Scalability Vertical scaling Horizontal scaling Highly scalable

Data May share a common Each service owns its own


Single centralized database.
Management database database
SOA (Service-Oriented
Aspect Monolithic Microservices
Architecture)

Can use different tech-


Technology
One tech-stack stacks but often still Polyglot architecture
Stack centralized.

Fault
Single point of failure Partial fault tolerance High fault tolerance
Tolerance

Best for small apps or legacy


Suitable for enterprise Ideal for cloud-native apps and
Use Case systems where simplicity
apps large, dynamic systems
matters.

A traditional e-commerce site A bank’s architecture — Netflix — with User Service,


with all functionality (cart, Payment Service, Loan Recommendations Service,
Examples payment, user management) in Service, Account Service Streaming Service — all
one project. — coordinated via an ESB. independent.
COMMON
TYPES OF
SERVICE-
ORIENTED
ARCHITECTUR
E
SERVICE ORIENTED ARCHITECTURE
SERVICE
ORIENTED
ANALYSIS
SERVICE ORIENTED ANALYSIS

OBJECTIVES GOALS

❖ Services to be built. ❖ Service operation candidates.

❖ Business logic to be used in each ❖ Group candidates into logical context.


service.
❖ Define service boundaries.

❖ Identify reusable logic


SERVICE ORIENTED ANALYSIS-STEPS

1.Define Business requirements


▪ Collect the documentation of the business requirements.
▪ Requirements should support service-oriented solution.
▪ Starting point for further process.
2.Identify automation systems
▪ Identify already existing logic for the requirements.
SERVICE ORIENTED ANALYSIS-STEPS(CONT..)

3. Model candidate services


▪ Identifying service operation candidates & group into logical context.
▪ Logical context -> service candidates.

Analysis phase proposes service candidates & service operation


candidates.
SERVICE
ORIENTED
DESIGN
Service-Orientation Design
Principles
SERVICE ORIENTED DESIGN- OBJECTIVES

❖ Derive physical service design from service candidates (Analysis phase).

❖ Required SOA characteristics.

❖ Required industry standards & extensions.


SERVICE ORIENTED DESIGN- GOALS

❖ Identify design standards. ❖ Set the boundaries of the architecture.

❖ Access support for service ❖ Define abstract service interface designs.


orientation principles.

❖ Identify potential service


compositions.

❖ Determine core set of


architectural extensions.
SERVICE ORIENTED DESIGN-STEPS

1.Compose SOA
SOA Fundamental Components
▪ XML data representation architecture.
▪ Web Services
▪ Vendor platform
SERVICE ORIENTED DESIGN-STEPS (CONT.…)

❖ Choose service layers.

❖ Position core SOA standards.

❖ Standardized logic representations


SERVICE ORIENTED DESIGN-STEPS (CONT.…)

2. Design Entity centric business services


❖ Represent the one service layer that is the least influenced by
others.
❖ Its purpose is to accurately represent corresponding data entities
(Database).
❖ Built for reuse by any application that needs to access or manage
information associated with a particular entity.
SERVICE ORIENTED DESIGN-STEPS (CONT…)

3. Design Application services


❖ The application service layer is a pure, service-oriented abstraction
of an organization's technical environments.
❖ Many real-world and technology-specific considerations need to be
taken into account.
❖ Application services can be the hardest type of service to design.
❖ E.g. Send Email, Send SMS, Send Notification, Transform data XML
to Native or Native to XML.
SERVICE ORIENTED DESIGN-STEPS (CONT.…)

4. Design Task-Centric Business services


❖The process for designing task-centric services usually require
less effort than the previous two design processes.
❖ Only the service operation candidates identified as part of the
service modeling process are addressed here.
❖ We are designing our task-centric business service after our
entity-centric and application service designs have been
completed. E.g. Invoice Process, Purchased Order Process
SERVICE ORIENTED DESIGN-STEPS (CONT.…)

5. Design Service-Centric Business process


❖ The orchestration service layer provides a powerful means by which
contemporary service-oriented solutions can realize some key
benefits.
❖ The most significant contribution this sub-layer brings to SOA is an
abstraction of logic and responsibility that alleviates underlying
services from several design constraints.
REFERENCES

◼ Service-Oriented Architecture: Analysis and Design for service and microservices Book
- By Thomas Erl
◼ Service-Oriented Architecture (SOA): Concepts, Technology, and Design
- By Thomas Erl
QUESTIONS?
THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy