'background-job' 검색 결과

Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Move slow Python operations into background jobs so requests can return promptly. Use task queues and workers, the processes that execute queued work, with retry rules, duplicate handling, time limits, and persistent job status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Send emails and notifications in the background
• Generate reports and data exports asynchronously
• Process uploads and media conversions

Implement reliable background job processing systems — queue management, retry policies, dead-letter handling, and distributed workers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements transactions, idempotency and interrupted-operation recovery; not schema migration or a mandatory background-job platform.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs background jobs in Node.js with BullMQ, a job queue library backed by Redis (or PostgreSQL since v6): delayed and prioritized jobs, retries with backoff, rate limiting, cron-style job schedulers, parent-child flows and concurrency control. Use when a user asks to add a background worker, queue emails or webhooks, schedule recurring jobs, retry failed jobs, rate limit an API client, or migrate from Bull or from BullMQ 5 repeatable jobs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pg-boss expert for PostgreSQL-backed job queues with exactly-once delivery, perfect for applications already using Postgres (Supabase, Neon, etc.). Use when "pg-boss, postgres queue, postgresql job, supabase background job, neon job queue, postgres scheduling, database job queue, pg-boss, postgresql, job-queue, background-jobs, supabase, neon, exactly-once, scheduling" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when "inngest, serverless background job, event-driven workflow, step function, durable execution, vercel background job, scheduled function, fan out, inngest, serverless, background-jobs, event-driven, workflows, step-functions, durable-execution, vercel, nextjs" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when "bullmq, bull queue, redis queue, background job, job queue, delayed job, repeatable job, worker process, job scheduling, async processing, bullmq, bull, redis, queue, background-jobs, job-processing, async, workers, scheduling, delayed-jobs" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour. Finds where the change will break before it is built, by walking ten named failure classes (twice, halfway, outside call, failure-is-not-empty, neighbors, endings, money, hostile user, words, scale and time) against the code, and writes the answers into the plan. Use when planning a change, when asked to "think it through", "cover the gaps", "make sure it's bug free", or before any edit to payment, publishing, deletion, auth or background-job code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates scheduled background jobs using Quartz.NET. Includes job definitions, triggers, cron scheduling, dependency injection, and persistent job store configuration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ", "Celery". NOT for real-time WebSocket communication, synchronous API calls, or simple setTimeout operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and implement backend service changes: API contracts, service boundaries, auth integration, reliability and delivery checks. Use for backend/API handlers, services, webhooks, jobs, or backend architecture changes. Routes schema/migrations to mk:database; security review to the existing security workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates scheduled background jobs using Quartz.NET. Includes job definitions, triggers, cron scheduling, dependency injection, and persistent job store configuration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ", "Celery". NOT for real-time WebSocket communication, synchronous API calls, or simple setTimeout operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs background job processing systems with queue integration (BullMQ/Celery), job definitions, retry policies, exponential backoff, idempotent execution, and monitoring hooks. Use when implementing "background jobs", "task queues", "async processing", or "job workers".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.