JobMaster proposes split-layer architecture to scale .NET jobs with centralized audit logs

A developer has outlined an architectural approach called JobMaster to address a long-standing trade-off in distributed .NET background job processing. Traditional schedulers like Hangfire and Quartz.NET offer strong audit trails and retry logic but struggle to scale due to database polling contention among worker instances. Message brokers scale well but lack native job-level auditing, retry tracking, and scheduling capabilities. JobMaster proposes separating execution from auditing by introducing an ephemeral 'Agent' layer for transient job execution and a persistent 'Master DB' for long-term audit history and coordination. This design aims to eliminate lock contention, maintain a centralized audit trail, and support high-throughput job processing across distributed workers.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in