Hi Will. Thanks for the video. Using azure service bus is the same way you did with Azure storage queues? I ve tried to do exactley as you do, provideing a connection string but It didn't work out
Hi Will. Thanks for the explaination and examples. On the scaling count side of the HTTP example, sounds like you're saying that if you configured min 1, max 10 instances/replicas, if requests exceed 100 then Azure will simply spin up 9 whole new instances, even if the request count is 101? I would sure think that firing up 9 extra instances to handle 1 request is a bit overkill? Or am I mistunderstanding? I would have thought that for every 100 requests above the initial count, Azure will fire up 1 extra instance to try handle the extra workload, so if 301 requests come flooding inbound, then there would be 3 instances having the requests being load-balanced between them?
Hey! If the requests exceed 100, then a new instance will spin up. So if 101 requests come in, and 1 replica is active, another one will spin up and you'll have 2 instances.
Let me add it to the backlog! Sorry I've taken a long time to respond, last year was a little crazy (moved to another country), so I'll look to do a step-by-step tutorial on this soon
Great question! So for Functions on ACA, you don't need to configure the KEDA scaled objects. It's designed to configure the scale parameters and rules as per event target: learn.microsoft.com/en-us/azure/azure-functions/functions-container-apps-hosting#configure-scale-rules However, for Cosmos DB, it looks like triggers can't dynamically scale yet. From that doc, it looks like it's just HTTP, Queue Storage, Service Bus, Event Hubs and Kafka triggers. Functions on ACA is still in preview, so I'd keep an eye on it.
Yes! You can use a custom scaling rule based on any ScaledObject-based KEDA scaler. This article on tech community has a good explanation of it: techcommunity.microsoft.com/t5/apps-on-azure-blog/scaling-options-in-azure-container-apps/ba-p/3878282#:~:text=You%20can%20create%20a%20custom,attention%20to%20detail%20is%20crucial.&text=The%20rules%20will%20scale%20the,the%20amount%20of%20Memory%20consumption.
Thanks very much for the really nice video. It was very clear and thorough. I hope you'll keep making videos about ACA!
Thanks @nchomey!
Hi Will. Thanks for the video. Using azure service bus is the same way you did with Azure storage queues? I ve tried to do exactley as you do, provideing a connection string but It didn't work out
Hi Will. Thanks for the explaination and examples. On the scaling count side of the HTTP example, sounds like you're saying that if you configured min 1, max 10 instances/replicas, if requests exceed 100 then Azure will simply spin up 9 whole new instances, even if the request count is 101? I would sure think that firing up 9 extra instances to handle 1 request is a bit overkill? Or am I mistunderstanding? I would have thought that for every 100 requests above the initial count, Azure will fire up 1 extra instance to try handle the extra workload, so if 301 requests come flooding inbound, then there would be 3 instances having the requests being load-balanced between them?
Hey! If the requests exceed 100, then a new instance will spin up. So if 101 requests come in, and 1 replica is active, another one will spin up and you'll have 2 instances.
Thank you very much for the video, can you show me step by step how to create a CPU based rule?
Let me add it to the backlog! Sorry I've taken a long time to respond, last year was a little crazy (moved to another country), so I'll look to do a step-by-step tutorial on this soon
is there any possibility to have 1 on 1 session ?
Thanks
If i am hosting a Azure Function in ACA. Can i somehow scale it if it uses a CosmosDBTrigger?
Great question! So for Functions on ACA, you don't need to configure the KEDA scaled objects. It's designed to configure the scale parameters and rules as per event target: learn.microsoft.com/en-us/azure/azure-functions/functions-container-apps-hosting#configure-scale-rules
However, for Cosmos DB, it looks like triggers can't dynamically scale yet. From that doc, it looks like it's just HTTP, Queue Storage, Service Bus, Event Hubs and Kafka triggers. Functions on ACA is still in preview, so I'd keep an eye on it.
is it possible to scale container app based on memory consumption?
Yes! You can use a custom scaling rule based on any ScaledObject-based KEDA scaler. This article on tech community has a good explanation of it: techcommunity.microsoft.com/t5/apps-on-azure-blog/scaling-options-in-azure-container-apps/ba-p/3878282#:~:text=You%20can%20create%20a%20custom,attention%20to%20detail%20is%20crucial.&text=The%20rules%20will%20scale%20the,the%20amount%20of%20Memory%20consumption.
Much appreciated
Thanks for watching!