u/SadViolinist2405

While documenting MQTT support in LavinMQ, I ended up digging through the broker internals and found something interesting architecturally.

Internally, MQTT subscriptions are mapped into queue-like structures while still preserving MQTT pub/sub semantics for clients.

That got me thinking:

If you were designing a broker that supports both AMQP and MQTT, would you:

• Keep completely separate routing systems?
• Translate MQTT concepts into queue-based internals?
• Or unify both protocols around a common abstraction?

One thing that surprised me is how much of MQTT can still leverage queue-oriented storage internally while presenting a pure pub/sub model externally.

Curious how people here think about multi-protocol broker design and protocol abstraction layers.