From b72165a5302e1fe2235b52d22fa4cede7ad18ef9 Mon Sep 17 00:00:00 2001 From: Aaron Schlesinger Date: Tue, 12 May 2020 15:05:18 -0700 Subject: [PATCH] s/constrainings/constraints --- concepts/actors/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/concepts/actors/README.md b/concepts/actors/README.md index 73d654129..77c04b935 100644 --- a/concepts/actors/README.md +++ b/concepts/actors/README.md @@ -24,7 +24,7 @@ Dapr includes a runtime that specifically implements the [Virtual Actor pattern] As with any other technology decision, you should decide whether to use actors based on the problem you're trying to solve. -The actor design pattern can be a good fit to a number of distributed systems problems and scenarios, but the first thing you should consider are the constraings of the pattern. Generally speaking, consider the actor pattern to model your problem or scenario if: +The actor design pattern can be a good fit to a number of distributed systems problems and scenarios, but the first thing you should consider are the constraints of the pattern. Generally speaking, consider the actor pattern to model your problem or scenario if: * Your problem space involves a large number (thousands or more) of small, independent, and isolated units of state and logic. * You want to work with single-threaded objects that do not require significant interaction from external components, including querying state across a set of actors.