Hi. I want to prevent the same event to be triggered more than once to prevent duplicated customer messages etc. According to the documentation we have:
- “If two events contain the same
id, we won’t process the event multiple times”
idmust be a ULID”
Item 1 is great and is what one would expect to prevent deduplication. I’m just wondering why item 2 is required. One could transform an existing id into a valid ULID, but that’s just additional complexity for apparently no benefit. Can someone clarify ?
Also, what would happen if we generate a ULID using a fixed constant timestamp (or the timestamp for the start of the day) and injecting an existing ID in the randomness part ? That would be a valid ULID. Would that work ?
Thanks in advance.
Best answer by katie_juddView original