Azure Container Apps #03 - Scale Out Containers | HTTP Based

Поділитися
Вставка
  • Опубліковано 3 лют 2025

КОМЕНТАРІ • 14

  • @olorundareagnes934
    @olorundareagnes934 3 місяці тому

    One of the best tutorials on Azure Container App! Thanks for these treasures.

  • @ratschi898
    @ratschi898 2 місяці тому

    Thanks bro your Tutorial is amazing

  • @tariqbilal503
    @tariqbilal503 6 місяців тому

    excellent, concise and clear video. Thanks

  • @santoshkumardash9934
    @santoshkumardash9934 9 місяців тому

    Awesome man .. this is great... Stuff... We are actually not aware of such amazing but simple videos... You are awesome

  • @amitmandhare-g1l
    @amitmandhare-g1l 7 місяців тому

    great man owsome job

  • @timroberts_usa
    @timroberts_usa 9 місяців тому

    good video-- very helpful. what load test tool did you use here??

  • @santoshkumardash9934
    @santoshkumardash9934 9 місяців тому

    One doubt I have is can we do custom api token validation in the container ingress? I mean custom API Authorization

  • @VioletClaw816
    @VioletClaw816 6 місяців тому

    once the replica is created, does it need to be manually removed if the request is getting low? thanks.

  • @GoranBralo
    @GoranBralo Рік тому +1

    just from curiosity is there any example for scaling container app based on memory :)

    • @subzeroleaf
      @subzeroleaf 10 місяців тому

      You have to use keda metrics.

  • @sumersinghrana8868
    @sumersinghrana8868 Рік тому +1

    What about scale down? Can these server terminated if request goes down?

    • @codecomposer88
      @codecomposer88 Рік тому +6

      Scale down is automatic. There is a scale down stabilization window of 300 seconds of waiting time before it goes from let's say 5 replicas to whatever lower number is needed, e.g. 3 replicas; so, when the condition are met for only 3 are replicas, it waits 300 seconds still holding the 5 replicas and then scales down to 3. Then later there is another 300 seconds of cool down period before it scales down to the minimum number of replicas (e.g. 0) when there is no need for more replicas than the minimum amount. BTW, the default scale up stabilization window is zero seconds, obviously :)

  • @youssefbenallal8289
    @youssefbenallal8289 Рік тому

    Normally there should be 20 replicas after running test with 400 threads and 20 concurrent requests for the scaling rule?

    • @codecomposer88
      @codecomposer88 Рік тому +1

      3:19 He set the maximum number of replicas to 5.