1 / 14

Atomic SOA Patterns

Atomic SOA Patterns. Elementary Middleware Communication Patterns for a Successful SOA Implementation Any complex communication scenario can be efficiently built from a small number of atomic patterns. SOA Application Layer Model (non-OSI).

eara
Download Presentation

Atomic SOA Patterns

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Atomic SOA Patterns • Elementary Middleware Communication Patterns for a Successful SOA Implementation Anycomplexcommunicationscenariocanbeefficientlybuiltfrom a smallnumberofatomicpatterns

  2. SOA Application Layer Model (non-OSI)

  3. Data exchangewithin a layerhappensalways via a Canonical Format. Data exchangebetweenlayersisonlydonethroughdefinedgateways. Canonical Data Transport von Neumann Paradigm of Computing: Communication as canonical 3-step process • Input • Process • Output János von Neumann zu Margitta: Mastermind of modern Computer Architecture

  4. Example: How to copy a file The quick & dirty approach Procedure CopyFile • Read the input file • Convert encoding • Save the file The atomic approach • Procedure readFile • Read the input file • ProcedureconvertEncoding • Convert encoding • Procedure saveFile • Save the file • Procedure CopyFile • Call inputFile • Call convertEncoding • Call saveFile

  5. Data Transport in Envelopes

  6. Interaction Transport/Data-Layer

  7. Atomic Patterns

  8. Sender

  9. Peer-to-Peer sink source M S R • Message directly from Sender to Receiver

  10. Peer-to-Peer with conversion source sink M m S R C source sink M m S R C • Message converted eitherby Sender or Receiver

  11. Message-Broker (Middleware) source sink MoM M m S R C • Message converted in a message-oriented middleware broker

  12. Message-Queue source sink MoM  M m S R C Q • Buffer message in queue until receiver is ready

  13. Message-Rerouting source sink MoM M S R C sink 2 Rule m R • Redirect message based on rules • e.g. Loadbalancing, quarantine

  14. Message Fan-out source MoM m M Sink 1 R S C sink 2 R Rule sink 3 R • Replicate messages based on rules • e.g. mass email

More Related