Skip to content

Add summary block and Temporal comparison to how-functions-are-executed#1512

Open
Benanna2019 wants to merge 3 commits intomainfrom
ben/dev-291-add-summary-block-and-temporal-comparison-to-how-functions
Open

Add summary block and Temporal comparison to how-functions-are-executed#1512
Benanna2019 wants to merge 3 commits intomainfrom
ben/dev-291-add-summary-block-and-temporal-comparison-to-how-functions

Conversation

@Benanna2019
Copy link
Copy Markdown
Contributor

Summary

Additive changes to /docs/learn/how-functions-are-executed based on Pat Holcomb's docs audit. This page has 2,218 views, a 7.09% subscription rate, and 1.9 avg views/user — users read it once and either convert or leave.

  • Summary block at top: Problem-framing paragraph before the existing intro. Positions Inngest against the complexity of alternatives (separate workers, custom runtimes, queue infrastructure). Designed for LLM citability per Pat's SEO/GEO recommendations.
  • Temporal comparison section: Added before Conclusion. Covers infrastructure, programming model, flow control, local dev, and self-hosting. Includes comparison table. Key differentiators: simple API with standard language primitives, no separate infrastructure, Dev Server with full local parity, flow control features available everywhere (not gated behind cloud-only pricing).

No existing content was modified.

Reviewer notes

  • Checkpointing: This page currently describes the HTTP-request-per-step execution model. Checkpointing has fundamentally shifted this (with HTTP as fallback). Should we add a note about checkpointing on this page, or is the current description still accurate enough? Would appreciate input from someone closer to the execution engine.
  • Temporal claims: Please verify the comparison points are accurate and fair, especially around Temporal's local dev tooling and their paid fairness feature.
  • Tone: Aiming for factual and specific without being aggressive. Feedback welcome.

Closes DEV-291">

DEV-291: Additive changes based on Pat Holcomb's docs audit.
- Summary block at top for LLM citability and problem-framing
- Temporal comparison section before Conclusion covering infrastructure,
  programming model, flow control, local dev, and self-hosting
@Benanna2019 Benanna2019 requested a review from djfarrelly as a code owner April 2, 2026 15:05
@linear
Copy link
Copy Markdown

linear bot commented Apr 2, 2026

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
website Ready Ready Preview, Comment Apr 2, 2026 5:41pm

Request Review

Removed the local development comparison paragraph and table row.
The original claim was based on a misread of internal Slack context
and needs proper verification before we can make any comparison
on Temporal's local dev experience.
@Benanna2019
Copy link
Copy Markdown
Contributor Author

Removed the local development comparison claim in the latest commit. The original claim was based on this Slack message from Tony where he was commenting on a specific piece of Temporal tooling, not their entire local dev experience. Need more context before we can make any comparison there.

@tonyhb if you have thoughts on what an accurate local dev comparison would look like, that would be a good addition in a follow-up.

- Change Temporal description from "most well-known" to "pull-based"
- Add connect/serve explanation to infrastructure paragraph
- Link flow control features to docs pages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants