<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft" -->

---
title: Explicit APIs vs Magic Directives | daily.dev
description: A comparison contrasts Vercel's newly launched Workflow Development Kit (WDK), which uses a build-time "use workflow" directive to make individual functions...
canonical: https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Explicit APIs vs Magic Directives | daily.dev
og:description: A comparison contrasts Vercel's newly launched Workflow Development Kit (WDK), which uses a build-time "use workflow" directive to make individual functions...
og:url: https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft
og:image: https://api.daily.dev/og/posts/WT3hGU7FT.png
og:image:alt: Explicit APIs vs Magic Directives
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Explicit APIs vs Magic Directives

**[Inngest Blog](https://daily.dev/sources/inngest)** · 14 min read · 0 upvotes · 0 comments

## Summary

A comparison contrasts Vercel's newly launched Workflow Development Kit (WDK), which uses a build-time "use workflow" directive to make individual functions durable, against Inngest's explicit step-based API using step.run() calls with IDs. Inngest's team, drawing on their own 2022 experience of abandoning implicit step IDs, argues explicit APIs provide compile-time type safety, straightforward testing and debugging, and—critically—stable state keys so deployments don't corrupt in-flight workflows. The piece walks through eight production scenarios (multi-tenant concurrency, rate limiting, fan-out, human-in-the-loop approvals, conditional and parallel steps, dynamic workflow composition, and cancellation) where Inngest's explicit, event-driven, compute-agnostic model is presented as better suited to coordinating thousands of concurrent workflows than WDK's directive-based, Vercel-locked durability layer.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.inngest.com/blog/explicit-apis-vs-magic-directives>

## Questions this post answers

### What is Vercel's Workflow Development Kit and how does it make functions durable?

Vercel's Workflow Development Kit (WDK) is a durability framework that uses a build-time "use workflow" directive to transform regular async functions into durable, crash-resistant routes with state persistence. It compiles code into isolated routes automatically, requires Vercel as the compute layer, and does not natively provide coordination, multi-tenancy, or queue-based flow control across concurrent executions.

_Developers comparing durable execution frameworks can track how workflow tooling evolves on daily.dev._

### Why did Inngest move away from implicit step IDs to explicit step IDs in its workflow engine?

Inngest switched to explicit step IDs after finding that implicit IDs, based on code position or line number, broke production workflows whenever a developer refactored code while a step like sleep or waitForEvent was mid-execution, corrupting state and forcing manual migration of run IDs via an API endpoint. Explicit IDs let code be refactored, reordered, or rewritten in another language while running workflows stay stable.

_Engineers debugging workflow state corruption during deploys can follow this trade-off discussion on daily.dev._

### What problems can occur when running thousands of concurrent workflow executions without flow control?

Without flow control, systems face thundering herd problems (10,000 events triggering 10,000 concurrent executions that overwhelm a database), rate limit violations from uncoordinated API calls, resource starvation where batch jobs block urgent customer workflows, and duplicate work from rapid repeated triggers. Concurrency limits, rate limiting, batching, throttling, and prioritization are needed to prevent these failure modes at scale.

_Teams scaling multi-tenant workflow systems can keep up with flow-control patterns like these via daily.dev._

## Similar posts on daily.dev

- [Durable AI Workflows 2026: Inngest, Trigger.dev, Vercel Workflow](https://daily.dev/posts/durable-ai-workflows-2026-inngest-trigger-dev-vercel-workflow-un2tgyyqs) · Alex CloudStar · 0 upvotes · 0 comments
- [A new programming model for durable execution](https://daily.dev/posts/a-new-programming-model-for-durable-execution-8hk6zrkca) · Vercel · 0 upvotes · 0 comments
- [On the way to step functions: the two worlds](https://daily.dev/posts/on-the-way-to-step-functions-the-two-worlds-anlwzk3po) · RUBYLAND · 0 upvotes · 0 comments
- [Automating Complex Workflow in Your Next.js App with Inngest](https://daily.dev/posts/automating-complex-workflow-in-your-next-js-app-with-inngest-z21aksfdw) · Telerik · 2 upvotes · 0 comments

---

Tags: [#architecture](https://daily.dev/tags/architecture), [#inngest](https://daily.dev/tags/inngest), [#vercel](https://daily.dev/tags/vercel), [#workflow-orchestration](https://daily.dev/tags/workflow-orchestration)

[View this post on daily.dev](https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Explicit APIs vs Magic Directives","url":"https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft"},"datePublished":"2026-09-13T19:57:26.269Z","dateModified":"2026-10-15T02:22:54.867Z","description":"A comparison contrasts Vercel's newly launched Workflow Development Kit (WDK), which uses a build-time \"use workflow\" directive to make individual functions...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/af5d2b26ba17a79735e3403bb17ea263?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/af5d2b26ba17a79735e3403bb17ea263?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Inngest Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Inngest Blog","logo":"https://media.daily.dev/image/upload/s--ieZKUa5y--/c_limit,w_256/f_auto,q_auto/v1789329423/logos/inngest?_a=BAMAMicg0","url":"https://daily.dev/sources/inngest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,inngest,vercel,workflow-orchestration","timeRequired":"PT14M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Inngest Blog","item":"https://daily.dev/sources/inngest"},{"@type":"ListItem","position":3,"name":"Explicit APIs vs Magic Directives"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/explicit-apis-vs-magic-directives-wt3hgu7ft#faq","mainEntity":[{"@type":"Question","name":"What is Vercel's Workflow Development Kit and how does it make functions durable?","acceptedAnswer":{"@type":"Answer","text":"Vercel's Workflow Development Kit (WDK) is a durability framework that uses a build-time \"use workflow\" directive to transform regular async functions into durable, crash-resistant routes with state persistence. It compiles code into isolated routes automatically, requires Vercel as the compute layer, and does not natively provide coordination, multi-tenancy, or queue-based flow control across concurrent executions. Developers comparing durable execution frameworks can track how workflow tooling evolves on daily.dev."}},{"@type":"Question","name":"Why did Inngest move away from implicit step IDs to explicit step IDs in its workflow engine?","acceptedAnswer":{"@type":"Answer","text":"Inngest switched to explicit step IDs after finding that implicit IDs, based on code position or line number, broke production workflows whenever a developer refactored code while a step like sleep or waitForEvent was mid-execution, corrupting state and forcing manual migration of run IDs via an API endpoint. Explicit IDs let code be refactored, reordered, or rewritten in another language while running workflows stay stable. Engineers debugging workflow state corruption during deploys can follow this trade-off discussion on daily.dev."}},{"@type":"Question","name":"What problems can occur when running thousands of concurrent workflow executions without flow control?","acceptedAnswer":{"@type":"Answer","text":"Without flow control, systems face thundering herd problems (10,000 events triggering 10,000 concurrent executions that overwhelm a database), rate limit violations from uncoordinated API calls, resource starvation where batch jobs block urgent customer workflows, and duplicate work from rapid repeated triggers. Concurrency limits, rate limiting, batching, throttling, and prioritization are needed to prevent these failure modes at scale. Teams scaling multi-tenant workflow systems can keep up with flow-control patterns like these via daily.dev."}}]}
```

