Skip to content

Commit

Permalink
Update daprdocs/content/en/developing-applications/building-blocks/ac…
Browse files Browse the repository at this point in the history
…tors/actors-overview.md

Signed-off-by: Hannah Hunter <[email protected]>
  • Loading branch information
hhunter-ms authored May 9, 2024
1 parent 2e1874b commit db6c251
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ You would use Dapr Workflow when you need to define and orchestrate complex work

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 numerical string for you as an ID in the Dapr SDKs.
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

Expand Down

0 comments on commit db6c251

Please sign in to comment.