Timeline for How to publish single event from multiple services
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2022 at 16:55 | answer | added | Hans-Martin Mosner | timeline score: 0 | |
| Dec 13, 2022 at 14:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 15, 2022 at 13:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 17, 2022 at 12:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 18, 2021 at 12:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 18, 2021 at 11:45 | answer | added | JavaTechnical | timeline score: 1 | |
| Oct 7, 2021 at 6:20 | comment | added | Alon Gouldman | @RikD I was thinking about events as if they where git diffs - every diff can be applied on the previous one, to get the full picture of the current state. If you have two notifications about the same event, would that not indicate that the event happens twice? (which is not true in my case, the event happened only once) | |
| Oct 6, 2021 at 17:05 | comment | added | Jon Raynor | @Alon - Yes when the event is stored, the storage mechanism knows something about the event that makes it unique and enforces that constraint. | |
| Oct 6, 2021 at 12:28 | comment | added | Rik D | The event handler should be able to handle multiple notifications about a single event. You seem to think that the message is the event, but that’s not true; the event is the thing that happened, the message is informing you about the fact that it happened. It shouldn’t matter if you are informed multiple times that the same thing had happened. | |
| Oct 6, 2021 at 8:27 | comment | added | Alon Gouldman |
@RikD so I will have two IpAddedEvent, and whoever cares about ips would know to treat both events as single? I was thinking about the event stream as the source of truth, and that would be wrong. I mean, if the events describe things that happen in the network, then there was only single IpAddedEvent
|
|
| Oct 6, 2021 at 8:23 | comment | added | Alon Gouldman | @JonRaynor do you mean that kafka (or similar solutions) knows not to store the same events twice, in case it has the same unique id? | |
| Oct 5, 2021 at 17:04 | comment | added | Rik D | Imo you’re trying to solve the wrong problem. Instead of trying to make the event unique, try to make the event-handler idempotent (able to handle the same event multiple times). | |
| Oct 5, 2021 at 15:50 | comment | added | Jon Raynor | You would need something to make the event unique, like IP address and event name. IP address would not be enough because other event could be sending you IP address data, so in this case its probably a combination of data elements. When the event is stored there is a unique constraint that avoid duplicates being added. Another consideration is tagging each event with a guid to make it unique and then other fields like event name, IP Address, Service Origin. Then technically there are different events, then just a query to dedup the IP addresses. That could work as well. | |
| S Oct 5, 2021 at 14:02 | review | First questions | |||
| Oct 5, 2021 at 14:55 | |||||
| S Oct 5, 2021 at 14:02 | history | asked | Alon Gouldman | CC BY-SA 4.0 |