Question 1

How to handle job failures in BusyBee?

Accepted Answer

Implement and register a custom IJobFailureHandler, as shown in the README's advanced usage section. This allows you to define error logging, retry logic, or other failure responses specific to your application's needs.

Question 2

Can BusyBee be used in a distributed system with multiple servers?

Accepted Answer

No, BusyBee is designed for in-memory, single-process scenarios and does not support distributed job queues. For multi-instance setups, you'd need an external message broker or a different library that handles coordination across processes.

Question 3

BusyBee vs Hangfire: which should I use for .NET background jobs?

Accepted Answer

BusyBee is better for lightweight, in-memory processing with built-in observability, while Hangfire offers persistence, scheduling, and distributed support out of the box. Choose BusyBee if you prioritize simplicity and performance within a single app; opt for Hangfire for more robust, production-ready features.

Question 4

How to set up OpenTelemetry metrics with BusyBee?

Accepted Answer

Use the AddOpenTelemetry method in your .NET app, configuring the tracing source and meter name provided by BusyBee (e.g., BusyBee.Observability.TracingConstants.TraceSourceName). The README includes a code example for integrating with Prometheus or console exporters.

Question 5

Does BusyBee support canceling jobs manually?

Accepted Answer

Yes, BusyBee provides manual cancellation support through IManualCancellationHandler. You can implement this interface to handle job cancellations, and the job context includes a CancellationToken for respecting cancellation in long-running tasks.

BusyBee

What is BusyBee?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions