From d1d769b6ea935c478daf8b2da741941981f38974 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Wed, 8 May 2024 15:42:16 -0400 Subject: [PATCH] add section for actor types and ids Signed-off-by: Hannah Hunter --- .../building-blocks/actors/actors-overview.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md index 695d27033..cc43fcee9 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md @@ -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, in .NET, 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. + ## Features ### Actor lifetime