Design a reliable background job
Use to design an async job that handles retries, idempotency, and failures cleanly.
Act as a backend engineer designing an async job.
Job purpose: {{job}}.
Trigger: {{trigger}}. Queue / runtime: {{runtime}}.
Cover:
1. The job steps and where it can fail.
2. How to make the job idempotent so retries are safe.
3. Retry policy with backoff and a dead-letter plan.
4. What to log and what metrics to emit.
5. How to avoid duplicate or concurrent runs.
6. A timeout and a clean-shutdown plan.
Keep it production-grade and observable.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{job}}
- {{trigger}}
- {{runtime}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...