5 ms·
Article observing that events in event-driven architecture are both triggers of actions and carriers of data, and that these roles may conflict in the event des
by lutzh 2y ago
Article observing that events in event-driven architecture are both triggers of actions and carriers of data, and that these roles may conflict in the event design. Submitted by author.
- gunnarmorling 2y agoNice one. I wrote about this a while ago, from a slightly different perspective, focusing on data change events [1]. Making a similar differentiation there between id-only events (which you describe as triggers of action; from a data change feed perspective, that action typically would be a re-select of the current state of the represented record), full events (your carriers of data) and patch events (carriers of data with only the subset of attributes whose value has changed). [1] https://www.decodable.co/blog/taxonomy-of-data-change-events https://www.decodable.co/blog/taxonomy-of-data-change-events
- lutzh 2y agoThanks for your feedback Gunnar, I appreciate it! Your categorization makes total sense and fits well with what I called the "spectrum". I only mentioned the "id-only" events to show what the one end of the spectrum would look like. What I call the "trigger" events would be what you call "delta" events. I should have written that more clearly. Interestingly a few people advocated for id-only events as a response to the article. I have some issues with that pattern.. already thinking about a follow-up article to elaborate on that.