Maestro v0.0.1 Maestro.Aggregate.Supervisor View Source

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

Link to this section Functions