Skip to main content

SOA – What is it?

 I couldn't find a universally accepted definition of SOA, which is why I have updated this post several times to include various perspectives on the topic.

In my understanding, Service-Oriented Architecture (SOA) is a style or approach to utilizing IT assets (such as software, hardware, networking, or other resources) as services. These services can be published in a shared repository, where consumers can browse available services, retrieve relevant information, and then invoke the service to place their requests.

It is crucial to manage these published services effectively because they are actively used by consumers. Therefore, service providers must adhere to specific contracts and conform to established standards; otherwise, consumers—and consequently, the business—will be negatively impacted.

From the above description, we can identify the following key components of SOA:

  1. Service Provider – The entity that offers and maintains the service.
  2. Service Consumer – The entity that utilizes the service.
  3. Registry/Repository – A directory where published services are listed, enabling consumers to discover and access them.
  4. Governance Body and Plan – A mechanism to oversee service production and ensure service quality.

Definitions of SOA

  • OASIS Definition:
    "Service-Oriented Architecture (SOA) represents a collection of best practices, principles, and patterns related to service-aware, enterprise-level, distributed computing."
    Source: OASIS

  • The Open Group Definition:
    "Service-Oriented Architecture (SOA) is an architectural style that supports service orientation. Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services."
    Source: The Open Group

  • MSDN Forum Discussion:
    A user on the MSDN Architecture Center Forum raised this question:
    "Service-Oriented Architecture is being touted as the next big thing in the IT world. I decided to do my master's dissertation on SOA and was surprised to find that there is no clear definition of SOA. As a starting point, I am trying to come up with a definition of SOA that will inform the rest of my research."
    The user further asks: "Can you offer a short definition of SOA?"
    Source: MSDN Forum

  • IBM Definition:
    "Service-Oriented Architecture (SOA) is a business-centric IT architectural approach that supports integrating your business as linked, repeatable business tasks or services."
    Source: IBM

Labels:

Comments

Post a Comment

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...
Post a Comment
Read more

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more