The Three Durable Function Forms: Orchestrators, Activities, and Entities (With Real Code)
The article discusses the three forms of Durable Functions: orchestrators, activities, and entities, emphasizing their distinct roles in managing workflows. It highlights common pitfalls that developers encounter when using these functions, particularly the confusion surrounding entities. The author provides practical examples and insights to help users effectively implement Durable Functions in their projects.
- ▪Durable Functions are designed to manage state across serverless function invocations.
- ▪The article explains the differences between orchestrators, activities, and entities, which are often misunderstood.
- ▪Entities are crucial for owning state, contrary to the perception that they are niche cases.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/ericwoooo_kr/the-three-durable-function-forms-orchestrators-activities-and-entities-with-real-code-57kk |
| Publication time | Fri, 22 May 2026 07:46:30 +0000 |
| Retrieval time | 2026-05-22T08:02:00.886Z |
| Last seen | 2026-05-22T08:02:00.886Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | JBVTyuDRFMKv |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3893397) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } 우병수 Posted on May 22 • Originally published at techdigestor.com The Three Durable Function Forms: Orchestrators, Activities, and Entities (With Real Code) #productivity #tools #webdev #discuss TL;DR: The thing that pushed me toward Durable Functions wasn't some architectural epiphany — it was a cron job graveyard.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
