chore(remove): event-hubs pump project #476
Open
Conversation
This file contains 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
stijnmoreels
added
integration:event-hubs
✅ Deploy Preview for arcus-messaging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Messaging library previously supported both Service bus and Event Hubs as message pumps. Due to maintainence costs, and the sheldom usage of message handling in event-sourcing systems, the maintainence cost for this is too high.
Related to the exercise described here #470 , this PR removes the Event Hubs message pump and related feature documentation. This can still be done in a minor release, as separate projects means separate NuGet packages. We only have to archive the NuGet package once we're finished with the release.