BrighterCommand/Brighter

[Feature] Support RMQ Streams

Open

#1818 opened on Nov 8, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)HTML (1,898 stars) (295 forks)batch import
.NET0 - BacklogV10.Xfeature requesthelp wanted

Description

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.

Contributor guide

Tech stack
csharp
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with BrighterRabbitMQ streamsKafka offset management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
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.