[Backend] backend/src/middleware/rate-limiter.middleware.ts and stream-rate-limiter.middleware.ts duplicate the same window/store setup logic

[grantfox-oss]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

backend/src/middleware/rate-limiter.middleware.ts and backend/src/middleware/stream-rate-limiter.middleware.ts both configure an express-rate-limit instance with a store and window, presumably repeating the same Redis/memory-store selection logic and key-generation boilerplate. Duplicated configuration means a fix to one (e.g. the trust-proxy IP-keying bug already tracked) has to be manually mirrored in the other.

Acceptance criteria

• Extract a shared createRateLimiter(options) factory used by both middlewares
• Migrate both files to use the shared factory
• Confirm existing rate-limiter tests still pass unchanged

Files to touch

• backend/src/middleware/rate-limiter.middleware.ts
• backend/src/middleware/stream-rate-limiter.middleware.ts

Out of scope

• Fixing the trust-proxy IP-keying issue itself (tracked separately)
• Switching rate-limit backends

[Peolite001]

@Peolite001 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peolite001 to this issue.

[sojetunde8]

@sojetunde8 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

PLease assign chief

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sojetunde8 to this issue.

[Bidex-cmyk]

@baedboibidex-cmyk has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

pls assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @baedboibidex-cmyk to this issue.

[martinshub-tech]

@martinshub-tech has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to take this issue. I've analyzed the root cause and am confident I can deliver a reliable fix with proper testing

ℹ️ Repo Maintainers: To accept this application, review their application or assign @martinshub-tech to this issue.

[JemimahEkong]

@JemimahEkong has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JemimahEkong to this issue.

[Ajibose]

@Ajibose has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

can i work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ajibose to this issue.

[olaleyeolajide81-sketch]

@olaleyeolajide81-sketch has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @olaleyeolajide81-sketch to this issue.

[Oyintarede]

@Oyintarede has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oyintarede to this issue.

[drips-wave]

Congratulations, @Peolite001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Peolite001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊