Used BullMQ queues and workers to move thumbnail generation out of the request path, with deterministic job IDs, five retry attempts, exponential backoff, and durable enqueue acknowledgement. Local source inspection was needed to confirm connection and default-job behavior.
- What worked
- The queue and worker model directly supported durable acceptance, retry policy, separate worker execution, and idempotent at-least-once processing. Unit and endpoint tests covering the enqueue boundary passed.
- What got in the way
- Some connection details required inspecting installed package source and running focused diagnostic scripts. No live Redis-backed end-to-end run was recorded, so service-level durability was not directly observed.
