Workflow Event Architecture

Summary

Workflow uses aggregate-raised domain events, save-time integration-event mapping, transactional outbox persistence and a hosted broker relay.

Event architecture

Boundaries

Aggregate changes and mapped outbox rows share the command save. Relay status updates occur later. The shared event bus publishes using event type as routing key without Workflow-owned queue declarations.

Maturity

Producer/outbox/relay are implemented. Consumer and callback orchestration remain Not implemented.

Requires Confirmation

Broker deployment, subscription ownership, callback bridge and monitoring require confirmation.

Source References

• microservices/src/workflow-service/Domain/Workflow/WorkflowInstance.cs
• microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs
• microservices/src/workflow-service/Messaging/OutboxRelayHostedService.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

Related Articles

• Events overview
• Event limitations
• Event source map

See Also

• Technical documentation
• Database documentation

Keywords

Workflow events, integration contracts, transactional outbox.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20