Support distributed dispatch consistency #135
Merged
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.
Allow strongly consistent command dispatch to work when Commanded is run on multiple nodes, but not formed as a cluster.
Phoenix's pub/sub library is optionally used since it supports broadcasting messages and tracking presence using PG2 or Redis. The Redis adapter can be used when running multiple nodes that are not connected together.
Usage
The new
Commanded.PubSub
behaviour defines basic pub/sub and process tracking functions. The default implementation uses Elixir's local-onlyRegistry
module.To use Phoenix pub/sub you must add it to your project's depedencies in
mix.exs
:Then configure the Phoenix pub/sub adapter you'd like to use:
The available options are:
Phoenix.PubSub.PG2
- uses Distributed Elixir, directly exchanging notifications between serversPhoenix.PubSub.Redis
- uses Redis to exchange data between servers