Service-Oriented Architecture (SOA) is a software design approach where services are the primary units of functionality. A service is a modular, self-contained unit that performs specific business tasks and communicates with other services via standard interfaces and protocols such as REST, HTTP, or SOAP. The core idea of service orientation is to promote loose coupling, reusability, scalability, and platform independence. Each service hides its internal logic (encapsulation), operates autonomously, and is reusable across different applications. This results in improved agility and efficiency within business and IT systems. SOA systems are built on several key principles: standardized service contracts, loose coupling, service autonomy, statelessness, reusability, discoverability, and composability. These principles help in creating flexible and manageable systems. Service orientation significantly impacts enterprises by enabling better integration of business functions, enhanced scalability, and reduced costs. Applications are built as compositions of services, promoting reuse and simplifying system upgrades. Integration becomes seamless through API-driven communication, service orchestration, and event-driven models. The four pillars of service orientation are teamwork, education, discipline, and balanced scope. These pillars support successful SOA adoption by ensuring collaboration, knowledge sharing, consistent practices, and well-defined objectives. Overall, Unit 1 provides foundational knowledge about SOA, its design principles, benefits, and enterprise applications. It sets the stage for understanding how service-oriented systems can modernize and streamline software development and deployment.

1. Service Oriented Architecture
Prepared By
Sundeep Challa|Meenal|Haleema Bushra|K. Ramesh

2. Introduction, Case Study Backgrounds
Unit - 1

3. Syllabus

4. Objectives
➔ Introduction
➔ History
➔ Technical Infrastructure
➔ Automation solutions
➔ Business Goals & Obstacles
➔ Case Studies
➔ Summary
➔ References

5. Introduction

6. What is Service?
➔ A service is a well-defined, self-contained function that represents a unit of
functionality.
➔ A service can exchange information from another service.
➔ It is not dependent on the state of another service.
➔ It uses a loosely coupled, message-based communication model to communicate with
applications and other services.

7. What is Service Bus?
➔ The Enterprise Service Bus (ESB) is a software architecture which connects all the
services together over a bus like infrastructure.
➔ It acts as communication center in the SOA by allowing linking multiple systems,
applications and data and connects multiple systems with no disruption.

8. Example
➔ Person carrying out a distinct task in support of other person is providing service

9. History

10. Technical Infrastructure

11. Automation solutions

12. Business Goals

13. Business Obstacles
➔ Management of Services Metadata: Services in SOA based environment require
exchange of a huge number of messages to complete the tasks. Management of the
interactions of such services is a complicated task.
➔ Security: When SOA is used, application-managed security is not suitable. Hence
separate technologies and standards have to be followed for this purpose.
➔ Shortage of Skilled Persons:
There is a shortage of manpower in integration and construction of services
infrastructure as the specification for SOA and Web Services are continuously
changing.

14. Business Obstacles
➔ Interoperability: Interoperability of SOA-based web services with existing stands is
a major challenge. For this basic profiles have been developed to enforce
compatibility with existing standards and technologies.
➔ Vendor Hyper: SOA-based product stacks are still under development and testing to
suite real world problems.SOA also guarantees reduced IT costs, improved systems
agility or faster time co-market only depending on the quality and relevance of the
system architecture and design.

15. Business Obstacles
➔ Business Service Governance and Auditing: Business services depend on a number
of other services. Defining policies and auditing compliance on these complex
dynamic relationships is challenging.
➔ Business Service Lifecycle Management: Business services require a collaborative
lifecycle management to ensure that consistent information is shared among
business peoples, developers and operators.

16. Business Obstacles Example

17. Case Studies
➔ Transit Line Systems
➔ Mid west University Association

18. Case Study - I
• Transit Line Systems

19. Case Study - II
• Mid west University Association

20. Summary

21. References