From 02b2ffa37f3a7bb99aca8a66909af3a63974d3a8 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Thu, 18 May 2023 14:34:06 -0400 Subject: [PATCH 1/6] add section for types and ids Signed-off-by: Hannah Hunter --- .../building-blocks/actors/actors-overview.md | 11 +++++++++++ 1 file changed, 11 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 eed8749691e..40b4b2d99e9 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 @@ -22,6 +22,17 @@ Every actor is defined as an instance of an actor type, identical to the way an +## Actor types and IDs + +To communicate with an actor, you need to know its actor _type_ and actor _id_. + +- **Actor type** uniquely identifies the actor implementation across the whole application. +- **Actor ID** uniquely identifies an instance of that type. + +If you don't have an actor `id` and want to communicate with a new instance, you can create a random ID. Since the random ID is a cryptographically strong identifier, the runtime will create a new actor instance when you interact with it. + +[Learn more about how each Dapr SDK handles actor types, actor ids, and actor interfaces.]({{< ref sdks >}}) + ## Dapr actors vs. Dapr Workflow Dapr actors builds on the state management and service invocation APIs to create stateful, long running objects with identity. [Dapr Workflow]({{< ref workflow-overview.md >}}) and Dapr Actors are related, with workflows building on actors to provide a higher level of abstraction to orchestrate a set of actors, implementing common workflow patterns and managing the lifecycle of actors on your behalf. From d1d769b6ea935c478daf8b2da741941981f38974 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Wed, 8 May 2024 15:42:16 -0400 Subject: [PATCH 2/6] 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 695d27033aa..cc43fcee932 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 From e1306972624b035f9c90f27e4e6dcc2ed6bb3423 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Wed, 8 May 2024 15:47:15 -0400 Subject: [PATCH 3/6] remove duplicate section Signed-off-by: Hannah Hunter --- .../building-blocks/actors/actors-overview.md | 11 ----------- 1 file changed, 11 deletions(-) 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 4d100f38b3b..cc43fcee932 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 @@ -26,17 +26,6 @@ Every actor is defined as an instance of an actor type, identical to the way an -## Actor types and IDs - -To communicate with an actor, you need to know its actor _type_ and actor _id_. - -- **Actor type** uniquely identifies the actor implementation across the whole application. -- **Actor ID** uniquely identifies an instance of that type. - -If you don't have an actor `id` and want to communicate with a new instance, you can create a random ID. Since the random ID is a cryptographically strong identifier, the runtime will create a new actor instance when you interact with it. - -[Learn more about how each Dapr SDK handles actor types, actor ids, and actor interfaces.]({{< ref sdks >}}) - ## Dapr actors vs. Dapr Workflow Dapr actors builds on the state management and service invocation APIs to create stateful, long running objects with identity. [Dapr Workflow]({{< ref workflow-overview.md >}}) and Dapr Actors are related, with workflows building on actors to provide a higher level of abstraction to orchestrate a set of actors, implementing common workflow patterns and managing the lifecycle of actors on your behalf. From 4e5e41df1c0455d5e0e1ddfb961ba9a1c1edbb7e Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Thu, 9 May 2024 09:23:15 -0400 Subject: [PATCH 4/6] added bit about what an actor id is Signed-off-by: Hannah Hunter --- .../building-blocks/actors/actors-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 cc43fcee932..ae3be62a826 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 @@ -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, 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. +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. ## Features From 2e1874b4b5192134bed6c4ebbb6a6466f0d6623b Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Thu, 9 May 2024 10:12:52 -0400 Subject: [PATCH 5/6] remove typo Signed-off-by: Hannah Hunter --- .../building-blocks/actors/actors-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ae3be62a826..b0ec44db4ac 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 @@ -54,7 +54,7 @@ You would use Dapr Workflow when you need to define and orchestrate complex work ## 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. +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. From db6c25192f6e6fc132193e3186aa5aa3a6c9a662 Mon Sep 17 00:00:00 2001 From: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Date: Thu, 9 May 2024 17:35:41 -0400 Subject: [PATCH 6/6] Update daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md Signed-off-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> --- .../building-blocks/actors/actors-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 b0ec44db4ac..fdde091390d 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 @@ -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