Async Patterns Skill

Not everything should happen in the HTTP request cycle. Background jobs, event-driven processing, and scheduled tasks are essential for scalable, resilient systems.

When to Activate

• A request triggers work that takes more than ~200ms (send email, generate PDF, call slow API)
• Processing that can fail and must retry (payment webhooks, third-party API calls)
• Scheduled recurring work (billing runs, cleanup jobs, report generation)
• Decoupling services via events (order placed → notify inventory, billing, notifications)
• Fan-out: one event triggers many downstream actions

Choosing the Right Pattern