Hi Liam,
Sorry for not being clear (English is my second language). Let me restate the situation as follows:
To de-abstract a little bit, suppose we have a class Customer, an instance of which has the following properties:
1) Customer Name: Paul.
2) It's defined in the global store 0.
2) it should be known (replicated) in stores 1, 3 and 5.
1) The UI or WebServices tier, where BusinessRules objects live, confirms some change made to Paul, and after validations the changes are packaged as a DTO (data transfer object) and sent to an AppServer.
2) Upon receiving the DTO, the AppServer will do the following ( S: synchronously, AS: asynchronously):
2.1) (S) Do some server side validation.
2.2) (S) Save the changed to the global store 0.
2.3) (AS) Do some post-processing stuff, like sending e-mails/communicator msgs to subscribers.
2.4) (AS) Deliver the changes to stores 1,3 and 5.
2.4.1) some of the stores, say 1 and 3, are located in the same db as store 0 (i.e., there is a num_store column in every table -multi-tenant architecture-)
2.4.2) some stores, say 5, are remote, accessible via low WAN connections.
What we're looking for is a technological way to accomplish item 2.4, and based upon your reply I see two different paths:
Path 1) Hub-and-spoke: The AppServer saves the information about the changes in some storage area; there are listeners working on behalf of each local store that will start sync sessions to receive the changes. I think this will be a scenario appropriate for MSF.
Path 2) Event-Based: The AppServer pushes the data to the local stores. If the local store is available, it commits the changes. If not, it will put the changes in a queue for later processing. This will involve more work and I don't know if MSF would be fit here.
I hope this is more understandable. Any Suggestions/Comments?
Thxs
Daniel
