Most background job frameworks are designed for server applications.
As an experiment, I built a demo showing the WJb background job engine running entirely inside a Blazor WebAssembly app. The demo executes jobs in the browser, tracks progress, updates UI in real time, supports chained actions, and demonstrates success, failure, and cancellation scenarios.
Key things demonstrated:
✅ Background job execution in a WASM environment
✅ Real-time progress tracking
✅ Chained actions
✅ Status handling (Completed / Failed)
✅ Live dashboard
✅ Decoupled action architecture
✅ Job cleanup support
One of my goals with WJb is to keep workflows and jobs as regular C# code instead of introducing DSLs, XML, or designers.
Source and demo:
👉 https://github.com/UkrGuru/WJb.Demo/tree/main/samples/WJb.Demo.Wasm
I'd be interested to hear from other .NET developers:
Would you ever run a job/workflow engine in the browser, and what use cases would justify it?
Top comments (0)