Player FM 앱으로 오프라인으로 전환하세요!
[Podcast] Handling Dependencies Between Subscribers in SOA
Manage episode 65045194 series 63841
In this podcast we answer questions about how to solve dependencies between systems that subscribe to events in SOA. We’ll also get into the pitfalls of employing distributed transaction when reusing existing systems even behind service boundaries.
Download via the Dr. Dobbs’ site.
Or download directly here.
And the original question was:
Udi:
I have a question regarding publishing events that relate to data changes. I found the article you wrote in the Arch Journal #8 very helpful. I think striving for autonomy is very important. The scenario I was thinking about is how can you ensure synchronization across subscribers of a particular event.
For example, System A publishes an event when customer information is updated. There are several systems that subscribe to this event. Two of the systems, System B and System C, need to be sync regarding customer information. System B uses operations from System C using the customer data. Using your example, System B has a process that runs for all “Preferred Customers”, and it uses processes on System C. However, System C may not have process the event to and may have a customer as preferred.
I have several thoughts, but would like to get your thoughts on this scenario. Are there any best practices or patterns?
Phil
Additional References:
- Autonomous Services and Enterprise Entity Aggregation (Article in Microsoft Architecture Journal)
- Podcast on Autonomous Services and Pub/Sub
You can find more episodes like this in the Ask Udi archives.
21 에피소드
Manage episode 65045194 series 63841
In this podcast we answer questions about how to solve dependencies between systems that subscribe to events in SOA. We’ll also get into the pitfalls of employing distributed transaction when reusing existing systems even behind service boundaries.
Download via the Dr. Dobbs’ site.
Or download directly here.
And the original question was:
Udi:
I have a question regarding publishing events that relate to data changes. I found the article you wrote in the Arch Journal #8 very helpful. I think striving for autonomy is very important. The scenario I was thinking about is how can you ensure synchronization across subscribers of a particular event.
For example, System A publishes an event when customer information is updated. There are several systems that subscribe to this event. Two of the systems, System B and System C, need to be sync regarding customer information. System B uses operations from System C using the customer data. Using your example, System B has a process that runs for all “Preferred Customers”, and it uses processes on System C. However, System C may not have process the event to and may have a customer as preferred.
I have several thoughts, but would like to get your thoughts on this scenario. Are there any best practices or patterns?
Phil
Additional References:
- Autonomous Services and Enterprise Entity Aggregation (Article in Microsoft Architecture Journal)
- Podcast on Autonomous Services and Pub/Sub
You can find more episodes like this in the Ask Udi archives.
21 에피소드
Minden epizód
×플레이어 FM에 오신것을 환영합니다!
플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.