Provide event bus for services #354
Merged
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
This adds a "service bus", accessible through `$api->bus`. It's intended for notifying other services about events or triggering actions that don't require the full audit capabilities of a Redis stream. It uses the sharded Redis pub/sub feature to avoid putting undue load on larger clusters (the publish/subscribe methods in the transport have been in place for a while, but used the old publish-to-all-shards PUBLISH/SUBSCRIBE calls).
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.
This adds a
->busmethod for lightweight notifications between services. It uses the Redis sharded pub/sub mechanism to send notifications between services.