inngest

# Inngest Integration Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. ## Principles - Events are the primitive - everything triggers from events, not queues - Steps are your checkpoints - each step result is durably stored - Sleep is not a hack - Inngest sleeps are real, not blocking threads - Retries are automatic - but you control the policy - Functions are just HTTP handlers - deploy anywhere that serves HTTP - Concurrency is a first-class concern - protect downstream services - Idempotency keys prevent duplicates - use them for critical operations - Fan-out is built-in - one event can trigger many functions ## Capabilities - inngest-functions - event-driven-workflows - step-functions - serverless-background-jobs - durable-sleep - fan-out-patterns - concurrency-control - scheduled-functions ## Scope - redis-queues -> bullmq-specialist - workflow-orchestration -> temporal-craftsman - message-streaming -> event-architect - infrastructure -> infra-architect ## Tooling ### Core - inngest - inngest-cli ### Frameworks - nextjs - express - hono - remix - sveltekit ### Deployment - vercel - cloudflare-workers - netlify - railway - fly-io ### Patterns - step-functions - event-fan-out - scheduled-cron - webhook-handling ## Patterns ### Basic Function Setup Inngest function with typed events in Next.js **When to use**: Starting with Inngest in any Next.js project // lib/inngest...