Commanded v0.16.0 Commanded.Registration behaviour View Source
Defines a behaviour for a process registry to be used by Commanded.
By default, Commanded will use a local process registry, defined in
Commanded.Registration.LocalRegistry
, that uses Elixir’s Registry
module
for local process registration. This limits Commanded to only run on a single
node. However the Commanded.Registration
behaviour can be implemented by a
library to provide distributed process registration to support running on a
cluster of nodes.
Link to this section Summary
Functions
Allow a registry provider to handle the standard GenServer
callback functions
Use the Commanded.Registration
module to import the registry provider and via tuple functions
Get the configured process registry
Link to this section Functions
Allow a registry provider to handle the standard GenServer
callback functions
Use the Commanded.Registration
module to import the registry provider and via tuple functions.
Get the configured process registry.
Defaults to a local registry, restricted to running on a single node, if not configured.
Link to this section Callbacks
Return an optional supervisor spec for the registry
Starts a uniquely named GenServer
process for the given module and args.
Registers the pid with the given name.
Return a :via
tuple to route a message to a process by its registered name
Get the pid of a registered name.
Returns :undefined
if the name is unregistered.