In the prior lesson (lesson 198) I discussed an anti-pattern associated with the number of derived events to trigger from a service. In this lesson I revisit the topic of derived events in event-driven architecture, but this time with regard to the payload of the event, and specifically how to avoid anemic events. An anemic event is one that doesn’t contain enough information to process the event. But how much information is not enough? How much information is too much? In this lesson I talk about the trade-offs associated with key-based events and full-data events, and then show how to avoid anemic events by sending just the right amount of information.
Software Architecture Monday: https://bit.ly/3dadEe3
Head First Software Architecture: https://amzn.to/3VNFI0o
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2