feat: publish EDC events to NATS#5741
Open
paullatzelsperger wants to merge 11 commits into
Open
Conversation
paullatzelsperger
force-pushed
the
feat/publish_events_to_nats
branch
2 times, most recently
from
d8995c9 to
c170ab4
Compare
jimmarino
approved these changes
May 12, 2026
wolf4ood
approved these changes
May 13, 2026
paullatzelsperger
force-pushed
the
feat/publish_events_to_nats
branch
from
7652808 to
140a670
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
this PR publishes all EDC events (subclasses from
Event) to a NATS stream.The stream is configurable, but the subject is
"events.<event-name>", e.g."events.asset.create". This allows for an easy subscription mechanismWhy it does that
to allow operators of EDC to consume events via message passing
Further notes
NATS was chosen because it is fast, small and easy to set up. In addition, a sister project https://github.com/eclipse-cfm/cfm already uses it with great success, so the integration is easy.
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes #5739
Closes eclipse-cfm/planning#52
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.