Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(guidelines): add new rule for sending durable event ids #77

Merged
merged 2 commits into from
Oct 7, 2024
Merged

feat(guidelines): add new rule for sending durable event ids #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c4b626
feat: add new rule for durable event IDs
JanKlasser3000 Aug 9, 2024
fc87a31
fix(docs): add proposed changes to durable event IDs rule
JanKlasser3000 Oct 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .../event-structure/rules/must-prepare-consumers-to-consume-events-idempotently.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@ As these requirements impose quite a restriction on the producer, a separate [`s
::: references

- [MAY provide `sequence` context attribute](../../../format/cloudevents/rules/may-provide-sequence-context-attribute.md)
- [SHOULD send durable event IDs ](should-send-durable-event-ids.md)
- [You cannot have exactly-once delivery](https://bravenewgeek.com/you-cannot-have-exactly-once-delivery/)
- [Exactly-Once Semantics Are Possible: Here’s How Kafka Does It](https://www.confluent.io/de-de/blog/exactly-once-semantics-are-possible-heres-how-apache-kafka-does-it/)
- [Processing guarantees in kafka](https://medium.com/@andy.bryant/processing-guarantees-in-kafka-12dd2e30be0e)
Expand Down
14 changes: 14 additions & 0 deletions ...idelines/async/semantics/event-structure/rules/should-send-durable-event-ids.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
id: R000058
---

# SHOULD send durable event IDs
JanKlasser3000 marked this conversation as resolved.
Show resolved Hide resolved

An event is a message that contains information about something factual that occurred in the past.
Each event must have an ID that identifies the event.
The event ID should be the same for retries or when sending via multiple channels. Consumers should assume that events with an identical source and ID are duplicates.

::: references

- [id message attribute in cloud event spec](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#id)
:::