How do you handle business process and workflows in an asynchronous event driven architecture? You can use event choreography and orchestration with compensating actions to overcome the lack of distributed transactions or two-phase commits in a distributed system. Here's how Event Choreography & Orchestration work and examples using NServiceBus.
🔔 Subscribe: [ Ссылка ]
💥 Join this channel to get access to source code & demos!
[ Ссылка ]
🔥 Don't have the JOIN button? Support me on Patreon!
[ Ссылка ]
📝 Blog: [ Ссылка ]
👋 Twitter: [ Ссылка ]
✨ LinkedIn: [ Ссылка ]
Sample Code:
[ Ссылка ]
0:00 Intro
0:44 Choreography vs Orchestration
2:13 Choreography Message Flow
4:31 Orchestration Message Flow
8:06 Compensating Actions
10:07 NServiceBus Saga
CodeOpinon: [ Ссылка ]
Twitter: [ Ссылка ]
Sagas: Event Choreography & Orchestration (NServiceBus)
Теги
event choreographysoftware architecturesoftware designdesign patternsprogrammingsoamicroservicesmessage queueskafkaevent busevent driven architectureazure service busrabbitmqdistributed transactionsservice busmass transitnservicebusmessage queuemessage queuingmessaging patternsservice oriented architecturemicroservice architecturedomain-driven designenterprise service busevent choreography vs orchestrationEvent choreography pattern
