[Feature] Support RMQ Streams · BrighterCommand/Brighter#1818

(2 留言) (0 反應) (0 負責人)HTML (1,898 star) (295 fork)batch import

.NET0 - BacklogV10.Xfeature requesthelp wanted

描述

Is your feature request related to a problem? Please describe. RMQ now supports streams as well as notifications, behavior is similar to Kafka. To be comprehensive in our support of popular brokers, we should support the streams model within Brighter

https://blog.rabbitmq.com/posts/2021/07/rabbitmq-streams-overview/

Describe the solution you'd like Model RMQ streams similarly to Kafka streams i.e. offset management etc. so as to make the two consistent. Delay and DLQ may be handled via RMQ though

Describe alternatives you've considered The main alternative is to assume anyone who wants streams will pick Kafka or Redis and we don't need to support this.

Additional context If someone is looking for a .NET framework for use with RMQ, and we don't support the usefuil feature set, folks will go elsewhere.

貢獻者指南

技術棧: csharp
領域: backend
議題類型: feature
難度: 4
預計時間: over 1 week
活動狀態: stale
清晰度: mostly clear
前置要求: Familiarity with BrighterRabbitMQ streamsKafka offset management
新手友善度: 20
研究方向: This feature request proposes adding support for RabbitMQ Streams in Brighter, modeled after existing Kafka stream support. To proceed, one should study the current Kafka stream implementation in the Brighter codebase (e.g., in the Paramore.Brighter.MessagingGateway.Kafka namespace) and understand how RabbitMQ Streams work via the linked blog post. Key challenges include offset management and deciding how delay/dead letter queues are handled—potentially using native RabbitMQ features. The issue has no assigned developer or linked PRs, so any contributor would need to propose a design first, likely starting a discussion in the issue comments.