My TOP Patterns for Event Driven Architecture

Here are my top 5 patterns and concepts (Outbox, Idempotent Consumers, Event Choreography, Orchestration, Retry/Dead Letter) for Event Driven Architecture that you'll likely implement. Why? Well if you're new to Event Driven Architecture there are many different problems that you'll encounter. Most of the issues have well-established patterns or concepts you can leverage to deal with them. Here are the most common patterns for Event Drive Architecture that you'll likely use.

🔗 EventStoreDB
https://eventsto.re/codeopinion

🔔 Subscribe:    / @codeopinion  

💥 Join this channel to get access to source code & demos!
   / @codeopinion  

🔥 Don't have the JOIN button? Support me on Patreon!
  / codeopinion  

📝 Blog: https://codeopinion.com
👋 Twitter:   / codeopinion  
✨ LinkedIn:   / dcomartin  

Reliably Save State & Publish Events (Outbox Pattern)
   • Reliably Save State & Publish Events ...  

Handling Duplicate Messages (Idempotent Consumers)
   • Handling Duplicate Messages (Idempote...  

Event Choreography & Orchestration
   • Sagas: Event Choreography & Orchestra...  

Handling Failures in Message Driven Architecture
   • Handling Failures in Message Driven A...  

0:00 Intro
0:25 Outbox Pattern
2:38 Idempotent Consumers
4:15 Event Choreography
5:46 Orchestration
7:36 Failures (Dead Letter Queues, Retries)

#eventdrivenarchitecture #microservices #messaging