Hi Mark

This is precisely captured by the serverless contract article I published 
recently:

https://medium.com/openwhisk/the-serverless-contract-44329fab10fb

Queue, reject, or add capacity as three potential resolutions under load. 

-r

> On Jul 18, 2018, at 8:16 AM, Martin Gencur <mgen...@redhat.com> wrote:
> 
> Hi Markus,
> thinking about scalability and the edge case. When there are not enough 
> containers and new controllers are being created, and all of them redirect 
> traffic to the controllers with containers, doesn't it mean overloading the 
> available containers a lot? I'm curious how we throttle the traffic in this 
> case.
> 
> I guess the other approach would be to block creating new controllers when 
> there are no containers available as long as we don't want to overload the 
> existing containers. And keep the overflowing workload in Kafka as well.
> 
> Thanks,
> Martin Gencur
> QE, Red Hat

Reply via email to