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

Examples 7: ArchiMate flow relationship between elements in layers

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...
Post a Comment
Read more

SmartSimpleTextGenerator: A Smarter Way to Generate Text

  Introduction In the world of text generation, simple n-gram models can produce decent results, but they often lack context-awareness and coherence. To address these limitations, I have developed SmartSimpleTextGenerator , an improved version of my previous project, ImprovedSimpleTextGenerator . This new version enhances the text generation process by integrating Part-of-Speech (POS) tagging , n-gram models , and a back-off strategy , making the generated text more meaningful and contextually relevant. Key Features of SmartSimpleTextGenerator ✅ N-Gram Model with POS Tagging – Uses trigrams (default n=3) and applies POS tagging for better word prediction. ✅ Back-off Strategy – If a trigram sequence is unavailable, it falls back to bigrams and unigrams to ensure smooth text generation. ✅ Sentence Tokenization & Structure Preservation – Tokenizes input text properly while maintaining sentence integrity. ✅ Randomized Word Selection – Generates diverse outputs rather ...
Post a Comment
Read more