Showing posts from April, 2013

Observer-Observable Idea in SOA

A traditional SOA platform is composed of individual web services. All the the flow of interaction scenarios of web services are designed from client to web services. Let me draw the architectural concepts basically. Basic UI - WS interaction scenario: blue part on UI indicates client stub codes to call WS All right, but; if this is an accessible application, there is something odd we have missed. What if we have to notify our clients, to update a critical information? Some naive argument goes like this: "We recommend you, to invoke our "getX" method in a short period of time". This offer needs to be more clear and certain. First of all, "recommend" is not indicating how crucial activity is, even if it is not an essential part of product. Also, "short period of time" is so ambigious term that can probably cause failures of users on run-time. Adding the observer web service that has single one-way method to listen changes on domain