![]() |
|
How would you structure a reliable background-job system for media generation? - Printable Version +- Sinisterly (https://sinister.li) +-- Forum: Coding (https://sinister.li/Forum-Coding) +--- Forum: PHP (https://sinister.li/Forum-PHP) +--- Thread: How would you structure a reliable background-job system for media generation? (/Thread-How-would-you-structure-a-reliable-background-job-system-for-media-generation) |
How would you structure a reliable background-job system for media generation? - Mxstermind - 10-26-2026 For a PHP application handling image generation, video processing and scheduled publishing, I'd avoid tying long-running tasks directly to a normal web request. A queue worker, explicit job states, bounded retries, idempotency keys and clear failure reporting make the workflow much easier to reason about. I'd also distinguish a generation failure from a publishing failure so retrying one doesn't duplicate the other. For developers who've shipped this in production, which queue and monitoring setup has worked best for you? |