I also prefer having the complete payload as part of the event. One case where we just gave the identifier was when we were interfacing with a third-party external app and there were some compliance matters involved in handing over all the data directly in the event.
I've been working on an Event-Driven System for the last year and I can't say how interesting it was. As with everything in Software Engineering, it has its pros and cons. One of the biggest benefits is the amount of decoupling between different services it gives.
Great post Raul.
I also prefer having the complete payload as part of the event. One case where we just gave the identifier was when we were interfacing with a third-party external app and there were some compliance matters involved in handing over all the data directly in the event.
Also, thanks for the mention!
Agree; compliance is one of the valid reasons not to send the payload.
Great point, Saurabh!
I've been working on an Event-Driven System for the last year and I can't say how interesting it was. As with everything in Software Engineering, it has its pros and cons. One of the biggest benefits is the amount of decoupling between different services it gives.
Awesome post Raul! 🙌
Well said, Petar; I actually think that's the major benefit!
The powerful thing of events that they can nicely decouple our system components. Comes with price, but many times it is reasonable.
Solid post brother, and thanks for the mention.
And decoupling is a powerful tool. It allows different parts of a system to function and evolve independently.
Thanks, Daniel!
Thanks for detailed post!
I am new to learning these concepts.
While i understand the theory and all, what do you recommend to do to apply these concepts?
I mean how would you identify EDA is the correct approach here etc.
Thanks in advance