Skip to content

Commit

Permalink
Merge pull request dapr#4139 from hhunter-ms/issue_1298
Browse files Browse the repository at this point in the history
[Actors] Section for types and IDs
  • Loading branch information
hhunter-ms authored May 28, 2024
2 parents 606d8ef + a8149d0 commit 27ec8b7
Showing 1 changed file with 6 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,12 @@ You would use Dapr Workflow when you need to define and orchestrate complex work

[Learn more about Dapr Workflow and how to use workflows in your application.]({{< ref workflow-overview.md >}})

## Actor types and actor IDs

Actors are uniquely defined as an instance of an actor type, similar to how an object is an instance of a class. For example, you might have an actor type that implements the functionality of a calculator. There could be many actors of that type distributed across various nodes in a cluster.

Each actor is uniquely identified by an actor ID. An actor ID can be _any_ string value you choose. If you do not provide an actor ID, Dapr generates a random string for you as an ID.

## Features

### Actor lifetime
Expand Down

0 comments on commit 27ec8b7

Please sign in to comment.