SOA

SERVICE ORIENTED
ARCHITECHTURE
FINAL PRESENTATION
 CONTENT:
• INTRODUCTION
• FOUR COMPONENTS
• HOW IT WORKS
• EXAMPLE OF UBER
• IMPLEMENTATION
• ADVANTAGES & DISADVANTAGES
• 9 PRINCIPLES
• HOW SOA & CLOUD COMPUTING WORK
TOGETHER
• CHALLENGES WHEN MERGING SOA
&CC
• CONCLUSION
 INTRODUCTION:
• Service-Oriented Architecture (SOA) is an
architectural style that provides a set of
principles and practices for designing
and building software systems.
• At its core, SOA emphasizes the creation
of modular, reusable, and loosely
coupled services, each representing a
specific business functionality.
• These services can be independently
developed, deployed, and consumed,
allowing for greater flexibility and
scalability in building complex
 COMPONENTS OF SOA

01 02 03 04
SERVICES: Building SERVICE CONSUMERS: SERVICE PROVIDERS: SERVICE REGISTRY:
blocks that perform Entities or applications Entities that create Entities that create and
specific tasks. that use services. and host services. host services.
Example: A weather Example: A mobile app Example: The Example: The company
service that provides that gets weather company or system or system that runs and
current weather updates from the that runs and maintains the weather
information. weather service. maintains the service.
weather service.
 HOW IT WORKS:
A service-oriented architecture (SOA) works
as an components provider of application
services to other components over a
network.
Service-oriented architecture makes it easier
for software components to work with each
other over multiple networks.
Service-oriented architecture is implemented
with web services (based on WSDL and
SOAP), to be more accessible over standard
internet protocols that are on independent
platforms and programming languages.
SOA EXAMPLE
Uber's platform is built on a
microservices architecture, similar to
SOA.
Different microservices handle tasks
like user authentication, geolocation,
and payment processing.
This modular architecture allows
Uber to scale its services
globally and introduce new features
independently.
IMPLEMENTING SOA: EXAMPLE OF WEB-SERVICE STANDARD:
When it comes to implementing
service-oriented architecture (SOA), An example of a web service standard is SOAP,
there is a wide range of which stands for Simple Object Access
technologies that can be used, Protocol.
depending on what your end goal is SOAP “is a messaging protocol specification for
and what you’re trying to exchanging structured information in the
accomplish. implementation of web services in computer
Typically, Service-Oriented networks.
Architecture is implemented with Although SOAP wasn’t well-received at first,
web services, which makes the since 2003 it has gained more popularity and is
“functional building blocks becoming more widely used and accepted.
accessible over standard internet Other options for implementing Service-
protocols.” Oriented Architecture include CORBA, or REST.
 Examples of SOA
Implementation:
SALESFORCE: FEDEX:

Industry: Customer Relationship

Industry: Logistics and Shipping
Management (CRM)
FedEx implemented SOA to streamline its
Salesforce is built on a multi-tenant
logistics and supply chain processes.
architecture that follows SOA principles.
SOA enables real-time tracking, efficient order
It offers a suite of cloud-based services like
processing, and seamless communication
Sales Cloud and Service Cloud, which are
between different systems involved in the
modular and can be customized to meet the
shipping and logistics workflow.
specific needs of different organizations.
ADVANTAGES OF SOA:
Scalability:
Services can be scaled independently, allowing
the system to handle varying workloads and
ensuring optimal resource utilization.
Maintainability:
SOA supports independent maintenance and
updates of services, minimizing disruptions to the
overall system.
.

Cost-Effectiveness:
Reusing existing services and optimizing
resource usage contribute to cost savings over
time.
:
DIS-ADVANTAGES OF SOA:
Dependency on Network:
SOA relies heavily on network communication; if the
network is unreliable, it may impact the overall
performance and availability of services.
Resistance to Change:
Organizations may face resistance to adopting SOA,
especially if it requires a significant shift in mindset
and practices.
.
Complexity:
Implementing and managing SOA can be complex,
requiring careful design, governance, and
coordination.
:
 9 PRINCIPLES OF
1. LOOSE COUPLING
SOA 2. INTEROPERABILITY
I. Definition: Services within SOA should be I. Definition: Services should be designed to
independent entities, meaning that changes operate seamlessly with each other,
to one service do not directly affect others. regardless of the technology or platform
II. Importance: Loose coupling enhances on which they are implemented.
flexibility and allows for easier modification, II. Importance: Interoperability ensures that
maintenance, and scalability of individual services can communicate effectively and
services. be easily integrated into larger systems.
 PRINCIPLES OF SOA
3. REUSABILITY: 4. Abstraction:
I. Definition: Services should be I. Definition: Services should
designed to be reusable in provide a well-defined interface
different contexts and by that abstracts the underlying
various applications. complexity of their
II. Importance: Reusable services implementation from service
reduce development time and consumers.
costs by promoting the use of II. Importance: Abstraction
existing components rather simplifies the interaction between
than building new ones from services, making it easier for
scratch. consumers to use and understand
the functionality provided by a
service.
 PRINCIPLES OF SOA
5. Discoverability: 6. Composability:
I. Definition: Services should be I. Definition: Services should be
discoverable through a central designed to be combined or
repository or service registry, orchestrated to create new, more
making it easy for service complex business processes.
consumers to find and access II. Importance: Composability
them. enables the creation of flexible
II. Importance: Discoverability and adaptive solutions by
enhances the visibility of combining existing services to
available services, promoting meet specific business
reuse and collaboration. requirements.
PRINCIPLES OF SOA 8. Statelessness:
7) Autonomy: I. Definition: Services should be
I. Definition: Services in SOA operate stateless, meaning that each request
independently and are responsible from a service consumer contains all
for their own processes and data. the information needed for the service
II. Importance: Autonomy enhances to fulfill that request.
the resilience and scalability of II. Importance: Statelessness simplifies
services, allowing them to function service implementation and promotes
independently and efficiently. scalability by eliminating the need to
store and manage session state.
9. Standardized Communication:
I. Definition: SOA relies on standardized
protocols and formats, such as SOAP
(Simple Object Access Protocol) or REST
(Representational State Transfer).
II. Importance: Standardized communication
ensures that services can understand and
interact with each other, enhancing
interoperability and reducing integration
challenges.
 How Service-Oriented Architecture And Cloud Computing

Work Together
First, it’s important to note that Service-
Oriented Architecture can work with or
without cloud computing, although more
and more businesses are moving file
storage to the cloud so it makes sense to
use cloud computing and Service-Oriented
Architecture together.
One downfall of using Service-Oriented
Architecture and cloud computing together
is that some aspects of it are not
evaluated, such as security and availability.
When using cloud computing, users are
often at the mercy of the provider.
CHALLENGES
WHEN MERGING
SOA & CLOUD
COMPUTING: There is one fairly major challenge businesses face
when merging cloud computing and Service-Oriented
Architecture is the integration of existing data and
systems into the cloud solution. There needs to be
continuity from beginning to end in order for there to
be a seamless transition.
It’s also important to keep in mind that not every IT
aspect can be outsourced to the cloud — there are
some things that still need to be done manually.
CONCLUSION:

In conclusion, service-oriented architecture (SOA)

offers numerous benefits such as flexibility,
reusability, and scalability.
It allows businesses to efficiently integrate disparate
systems and enables the development of robust and
agile applications.
By adopting SOA, organizations can achieve better
collaboration among different services, improve
efficiency, and enhance their overall digital
transformation efforts.
THANK YOU
PRESENTED BY:

MUSTAFA SHEIKH
DANIYAL HAIDER
HAFSA MAZHAR