Jobs Worker Messaging And Execution Model
Purpose
This functional area defines how background work is received and executed.
Main Capabilities
- MassTransit consumer execution
- configurable transport support for background processing
- in-memory execution for local development and RabbitMQ-backed execution for brokered deployments
- retry-enabled background processing
- shared consumer hosting for enrichment, retention, and governance-related workloads
Functional Value
This area gives the platform a reliable asynchronous processing model across components.
Long-Running Work
Some background workloads, such as LLM-driven mapping enrichment, can run for an extended period. The platform is designed so that a long-running job is never simply left to the messaging transport — each such workload has its own means of detecting an interrupted run and recovering it without redoing work that has already been paid for.
See Jobs Worker Semantic Enrichment Processing for how this applies to enrichment jobs specifically.
