Some More SOA Design Patterns

Share the article!

Did some more googling around and have uncovered a couple more noteworthy SOA patterns. These are from the following sources:

  • Agent Itinerary – Objectifies agent itineraries and routing among destinations.
  • Forward – Provides a way for a host to forward newly arrived agents automatically to another host
  • Ticket – Objectifies a destination address, and encapsulates the quality of service and permissions that are needed to dispatch an agent to a host address and execute it there
  • Delegation – The debtor of a commitment delegates it to a delegatee who may accept the delegation, thus creating
    a new commitment with the delegatee as the new debtor.
  • Escalation – Commitments may be canceled or otherwise violated. Under such circumstances, the creditor or the
    debtor of the commitment may send escalations to the context Org.
  • Preemption – To cancel a commitment based on conflicting demands.
  • Barrier – Guards an action and specifies (pre)conditions on its execution
  • Co-location – Two or more resources are to be co-located at a certain time and place for a specified duration.
  • Correspondence – Relating two pieces of information each owned by a different participant
  • Deadline – Some information is required for an action before a certain time after which an alternate action is taken
  • Expiration – Some information will become invalid at a certain point in time (not shown in figure)
  • Notification – On-state-change xe2x80x9cpushingxe2x80x9d of information to enforce Correspondence.
  • Query – On-demand periodic polling of information to enforce Correspondence
  • Retry – Retrying an action a number of times before resorting to an alternate action
    Selection Choosing from among similar service offerings from multiple participants according to some criteria
  • Solicitation – Gathering information about service offerings from participants
  • Token – Issuing a permission for executing an action to other participants
  • Saga – How can we get transaction-like behavior or complex interactions between services without transactions.
  • Obligation Management – Allow obligations relating to data processing to be transferred and
    managed when the data is shared
  • Sticky Policies – Bind policies to the data it refers to

A couple of them are redundant with other patterns in other texts. You can find these patterns here:

Share the article!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>