http-add-on VS rsyscall

KEDA ships with an HTTP add-on to enable HTTP scaling.

KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.

I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.

If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.

(You're of course welcome to just go pick up an issue in the repo if you'd prefer)

The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.

Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:

First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.

Can you say what left you confused?

I'm surprised, I thought https://github.com/catern/rsyscall is pretty self-contained and self-explanatory (if unclear on what exactly rsyscall is useful for), and I thought http://catern.com/integration.html is quite detailed (perhaps excessively so).

That's one of the things I use this kind of primitive for in https://github.com/catern/rsyscall