Please enable JavaScript.
Coggle requires JavaScript to display documents.
SOA - Coggle Diagram
SOA
state of art
why
Extensibility
integrality
interoperability
Goals
Reusability
hide distribution
avoid herogeneity
uniformization
Communication
synchronously
Obtain immediate responses of the communication
Require an "always-available" server
follow a request/reply parttern
The client implements busy "waits" after each request in order to be ready to receive the response from the server side
asynchronously
Partner creates a message to the destination
communicating partterns are decoupled
request/reply parttern is not applied
mediator
intermediate entity
no immediate response
Server or remote partner not expecited to be "always available"
Middleware
ORB
RPC
MOM