Maestro v0.3.1 Maestro.Aggregate.Supervisor View Source
Supervisor for Maestro.Aggregate.Root
s across any/all domains.
All aggregate roots, no matter how many different kinds you may have, are managed by a single supervisor/registry (for now). Given that aggregates are independently configurable and extensible, the need for a 1:1 on supervisors per aggregate is a premature optimization. Furthermore, aggregate IDs are HLC timestamps and are thus unique even across aggregates.
Link to this section Summary
Functions
Returns a specification to start this module under a supervisor.
Callback invoked to start the supervisor and during hot code upgrades.
Link to this section Functions
child_spec(arg) View Source
Returns a specification to start this module under a supervisor.
See Supervisor
.
get_child(key, mod) View Source
init(args) View Source
Callback invoked to start the supervisor and during hot code upgrades.
Developers typically invoke DynamicSupervisor.init/1
at the end of
their init callback to return the proper supervision flags.
Callback implementation for DynamicSupervisor.init/1
.