integration - Publish Subscribe - Data Synchronisation between Legacy Applications -
i looking resolve issues data synchronisation implemented on integration platform, , have questions business logic should sit when using publish / subscribe pattern.
the integration solution uses triggers created in 2 customer management systems implement logic filters events / changed records should marked synchronisation. example of simple , more complex scenario has been implemented creating complex filtering , event/record triggering in each sources system shown below :
- business rule :only integrate customers , persons related customers
- scenario 1 :person customer role – mark record outbound integration person has role of customer
- scenario 2 :relationship created between customer , non customer – mark non customer outbound integration ( create outbound messages person, address, phone details etc ) , mark relationship record outbound integration.
this data synchronisation point point integration architecture perspective, messages routed other system directly (even though solution implemented using network of rest services / components). our vendor has reviewed solution , has instructed components need modified incorporate publish / subscribe pattern, enable addition of 2-3 customer management systems in our project pipeline.
this questions have implement design of business logic mediates records integrated, particularly given long term situation 4 systems creating , consuming changes in data synchronisation.
- question 1: should business logic determine records should integrated built integration layer , no modification should done applications being data synchronised (that is, refrain building logic in triggers )
- question 2: general principle of in publish / subscribe publishing system should publish records data element being synchronized, , logic filter whether records should or should not integrated implemented in each subscriber?
any advice, or pointers practical discussion of above appreciated.
thanks kindly
dels
Comments
Post a Comment