The Dual Nature of Events in Event-Driven Architecture

Re:The Dual Nature of Events in Event-Driven Architecture by hcarvalhoalves on Saturday November 02, 2024 @12:42PM (#42027454)

Yes, it happens. A way to deal with it is carrying some counter on the message metadata and incrementing it every time a consumer passes it along, so you can detect recursions. Another is having messages carry a unique id, and consumers record already seen messages.

[ Parent | on HN ]

Re:The Dual Nature of Events in Event-Driven Architecture by switch007 on Saturday November 02, 2024 @01:44PM (#42027883)

Do you consider it a requirement for every message?

Like, the problem sounds bad enough to warrant it. If not, now do you choose when to apply it?

Our architects have a habit of ignoring these kind of issues and when you suggest making things like this a requirement they accuse you of excessive concern!

[ Parent | on HN ]

Re:The Dual Nature of Events in Event-Driven Architecture by hcarvalhoalves on Saturday November 02, 2024 @07:33PM (#42030022)

I've worked with a codebase in the past that would handle this transparently with some sort of middleware for consumer/producer.

[ Parent | on HN ]