chessmadra-frontend VS http-add-on

Create a repertoire with ChessMadra

Listudy: Memorise openings with spaced repetition. Chess Endgame Training Chessercise: Practice chess with YouTube. Chess Madra: Build and practise an opening repertoire. Aimchess: Learn your strengths and weaknesses.

Chess Madra for building and practicing an opening repertoire.

Also there is always Chessmadra where you can build an opening repertoire tailored to the moves you encounter at your rating.

Check out ChessMadra. It's more of an opening repertoire builder than "randomly selected", but with spaced repetition.

It doesn't make much sense to study openings to an absurd depth, as you said. Opening principles are much more important as soon as you are taken out of book. But It should be possible to build your repertoire with the Catalan in mind for your rating range with ChessMadra. Put in your rating range, build and drill it.

I use chessmadra.com. Works pretty well for building a repertoire and practicing, plus had access to lichees opening database. Is completely free.

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.