Software Architecture Monday with Mark Richards is a free bi-weekly software architecture lesson containing a short video about some aspect of software architecture. These lessons contain tips, techniques, and advice to help you in your journey from developer to architect. New lessons will be posted every other Monday. You can see an index and description of each video by going to https://www.developertoarchitect.com/lessons/
Curated by: Software Architecture Monday (221 videos)
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