You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I have an app installed by 100,000 repositories each sending events every minute, and my workload is heavy, how can I distribute the load to a cluster of workers?
I can't find any documentation that describes how smee.io and probot handles this. Is it assumed that at any given time, there is only one instance subscribing to all webhook events that are sent to my app? That seems difficult to scale and ensure high availability - what if this single instance goes down? We'll then just miss some events? Or are there mechanisms in place that can deal with load balancing and guaranteed at least once/exactly once delivery?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Let's say I have an app installed by 100,000 repositories each sending events every minute, and my workload is heavy, how can I distribute the load to a cluster of workers?
I can't find any documentation that describes how smee.io and probot handles this. Is it assumed that at any given time, there is only one instance subscribing to all webhook events that are sent to my app? That seems difficult to scale and ensure high availability - what if this single instance goes down? We'll then just miss some events? Or are there mechanisms in place that can deal with load balancing and guaranteed at least once/exactly once delivery?
Beta Was this translation helpful? Give feedback.
All reactions