6 ms·
What’s wrong with a autoscaling container behind an load balancer that has a http handler with optionally a pub sub in between? Security, retry etc are not hard
by TeeWEE 4y ago
What’s wrong with a autoscaling container behind an load balancer that has a http handler with optionally a pub sub in between? Security, retry etc are not hard. You could use a service mesh. Why not use k8s
- subomi 4y agoIt's the usual how difficult can this be to build and operate. But what we've found is it's a pain at scale. - How do you ensure that one or a set of bad endpoints do not clog the queueing system and delay delivery of other working endpoints? - How do you provide easy tools for developers across projects to debug and fix webhook delivery problems? - How do you ensure this container is multi-tenant to serve multiple teams and no two teams can view each other data? - How do you ensure flexibility if a new team decides to use RabbitMQ instead of Kafka? Once you start to factor in all this requirements & more, you eventually build your own Convoy. :) TLDR: Convoy is that container that is flexible and powerful enough to manage all your webhooks needs.