Service
Service is Pulsar’s consumer-audience delivery boundary, grouping routes, providers, and feature modules.
Generated facts
- Layer
- service
- Generated path
app/Pulsar/Services/{Service}- Generator command
make:service- Workflow method
- None
- Stability
- Current manifest surface (Pulsar 0.4.1)
Canonical example
Responsibility
Service owns the responsibility stated above; it must not absorb delivery, transaction, or unrelated cross-layer behavior.
Placement and dependencies
Keep this type in its generated Service Module path. It may depend inward on Domain capability, but it must not make another Service its behavioral dependency.
Workflow and tests
Service is consumed by the owning Domain or Service workflow and returns a delivery-neutral result. Test its direct contract, its rejected boundary cases, and the caller or callee that proves the rule in application flow.
Three pitfalls
- ❌ Prohibited: move this responsibility into a neighboring type merely because it is nearby.
- ✅ Correct: keep the generated placement and depend only on the documented layer direction.
- ✅ Correct: test the boundary through the caller and the return or side effect visible to its callee.
Related reading
Read architecture placement for shared rationale and follow this page’s related concept links for the adjacent responsibility.
Boundaries
❌ Prohibited: A Service must not represent a microservice, database boundary, or deployment unit.
✅ Correct: Keep delivery concerns scoped to an audience and share business capability through Domain.