pnoker eeffe6fa59 docs(design): add mq abstraction design with mqtt boundary ...

Add the pluggable message broker ADR (docs/design/mq-abstraction.md):

- port + one adapter per broker, selected by dc3.mq.type (default rabbitmq)
- two subscription modes (LOAD_BALANCE / BROADCAST), batch consumption with
  post-commit batch ack, bounded redelivery, lease-coupled instance expiry
- eight broker-specific semantics mapped per target broker with documented
  fallbacks (delay -> local scheduler, JMS confirm -> driver outbox)
- capability matrix, 13-case TCK as the community adapter acceptance bar,
  three-phase wire-compatible migration plan
- mqtt boundary (7.1): device-access plane stays vendor-neutral by protocol,
  internal plane may run over any mqtt 5 broker via a dedicated adapter

Status: proposed; phase 1 (port + rabbitmq adapter + business migration)
implemented in the follow-up commits.

2026-08-19 18:47:15 +08:00

..

design

docs(design): add mq abstraction design with mqtt boundary

2026-08-19 18:47:15 +08:00