BrighterCommand/Brighter

[Feature] MQTT not have Brighter standard messaging gateway

Open

#3901 opened on Nov 5, 2025

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

Description

Describe the bug

The current implementation on MQTT doesn't have a custom ChannelFactory, MessageProducer and other

Further technical details

  • Brighter version: 10.0.01

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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
C#Brighter framework basicsMQTT protocol basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue requests adding missing MQTT implementation components (ChannelFactory, MessageProducer). First, review existing transport implementations (e.g., Kafka, RabbitMQ) in the Brighter repository to understand the pattern. Check the MQTT related code already present, likely in src/Paramore.Brighter.MessagingGateway.MQTT/. Examine linked PRs or comments for any existing partial work. The issue body is vague, so clarification from maintainers may be needed on which specific components are missing and acceptance criteria.