From d05d081072f068ad17691c0661d389a80554c452 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Thu, 8 Aug 2024 14:31:30 -0400 Subject: [PATCH] add note about default app-max-concurrency Signed-off-by: Hannah Hunter --- .../content/en/operations/configuration/control-concurrency.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/daprdocs/content/en/operations/configuration/control-concurrency.md b/daprdocs/content/en/operations/configuration/control-concurrency.md index c33828285..94dd9e7d8 100644 --- a/daprdocs/content/en/operations/configuration/control-concurrency.md +++ b/daprdocs/content/en/operations/configuration/control-concurrency.md @@ -8,6 +8,8 @@ description: "Learn how to control how many requests and events can invoke your Typically, in distributed computing, you may only want to allow for a given number of requests to execute concurrently. Using Dapr's `app-max-concurrency`, you can control how many requests and events can invoke your application simultaneously. +Default `app-max-concurreny` is set to `-1`, meaning no rate limits are set. + ## Different approaches While this guide focuses on `app-max-concurrency`, you can also limit request rate per second using the **`middleware.http.ratelimit`** middleware. However, it's important to understand the difference between the two approaches: