Great video, great introduction to this vast topic

Another amazing video, would also appreciate it if you would create a small end to end web api, ddd architecture project showcasing these concepts in an end to end project…

Amazing! meaningful video. Thank you for sharing!

Great video! It would also be great if you could add scenarios where EDA is not suitable, i.e. it's simpler and cheaper to make those HTTP/gRPC calls instead

THIS IS LITERALLY THE BEST EDD Video I’ve seen ever

Nice explanation. Do you have any book recommendation on EDA?

Very informative video! Some follow-up questions- 1) I am having trouble understanding the difference between #2 and #4. Are they not both trying to orchestrate an internal process? 2) i have been trying to figure out how granular the events need to be. We have a Human Resources system, where they are trying to support Enterprise events that span use cases #1. 3 where the goal is to notify downstream systems of data change. We are evaluating the granularity of the events - e.g. it could be New Hire or Promotion or Separation, or one could go granular e.g. new hire future, new hire retro, new hire onboarding. When the consumers get the events, they have to make a call back to get the change. Do we in such a case define the granularity of the events based on the use cases and consumer needs? I have come across event storming but for use case #1, we don’t need to have events for things that are not relevant for the use case e.g. say item added to wish list. Sorry for the long question! I have been trying to understand this but haven’t been able to find any resources. Any pointers would be greatly appreciated.

Do you have any views on syncing 'from' an external system? That is, pulling in a list of products on a regular, scheduled job? Btw great content from your channel!

Great video! But I was wondering if event-driven fits most of the cases in the late life-time of a project? I think there's a complication overhead with adding a broker and using event-choreography instead of having the whole work-flow in one place. From your experience you think it is worth it to start from the beginning with an event-driven architecture? or start with something simpler like service architecture and refactor later if things started getting complicated ?

Thanks for the video. The last part of it about temporal decoupling raised a question for me: What if we have a system where we have to fail after a while if one of the service is not responding. Since we are not waiting this service to do it's job, how we are going to know there is a failure? Setting a timeout for certain events to occur?

When would you use queues over topics, seems like in my company we always have one queue per consumer and just publish messages there

Which way do you want those events to flow typically?

2 videos in a week… 🎉

Regarding temporal decoupling example, in NodeJs we can call warehouse and billing related methods asynchronously ( may catch them in their respective catch methods ). So, I believe that's correct and we may not need decoupling if we write code like that. Please comment. I do know you are explaining it from event driven architecture perspective but Node.Js is event driven, although we don't save those event like the kafka does. PS: I like the way you explain things by code and example.

What would happen if the Event Broker is unavailable?

I like to categorize events in 3 different "archetypes": - Domain events - RESTful events - Signal events

how is this video dated 11 MAy 2022 and today is May 8th???