ADR 0013 — Messaging ack model for Logic Apps import¶
Status: Accepted (direction)
Date: 2026-08-10
Related: Logic Apps Standard import,
Egress RabbitMQ — Consumer ack vs peek-lock,
RabbitMQ broker
Context¶
Logic Apps Service Bus flows often use peek-lock receive plus a later
complete*MessageV2 action (lock token). MeshFlows AMQP triggers on RabbitMQ
ACK/NACK in the subscriber after a synchronous Orchestrator invoke — there is
no workflow step that completes a delivery token.
Operators migrating from Logic Apps ask whether MeshFlows should:
- Keep RabbitMQ and document the model mismatch, and/or
- Add step-level ack, and/or
- Introduce another open-source broker with stronger “ack from consumer / app” APIs (Pulsar, NATS JetStream, Artemis, Redis Streams, …).
Decision¶
- Default: remain on RabbitMQ /
meshflows.eventswith subscriber-owned ACK for trigger paths. Import scaffolding dropscomplete*steps and emits AMQP trigger stubs instead. - Preferred evolution (if LA parity pressure rises): a step-level ack API (deferred delivery token held by the subscriber, completed/abandoned from a capability or orchestrator callback) — not a second broker by default.
- Second-broker candidates only if product needs go beyond RabbitMQ:
- NATS JetStream or Apache Pulsar for explicit / deferred ack patterns closer to “complete from application”.
- Artemis if JMS/AMQP shops dominate.
- Redis Streams (
XACK) for lightweight PEL-style ack — not a full ESB replace. - Kafka is not treated as peek-lock complete: offset commit is partition progress, not a lock-token complete from an arbitrary workflow step.
Consequences¶
- Analysis reports mark
complete*MessageV2as unmapped; scaffolding comments explain subscriber ACK. - Wiki reference 22 carries the broker comparison table for operators.
- No new broker dependency is introduced by the Logic Apps import MVP.
- A future design for deferred ack should specify token storage, timeout, and
multi-replica safety before exposing a
completestep.
See also¶
- Broker comparison table: 22 — Peek-lock alternatives
- ADR 0012 (MSI / workload identity — separate concern)
- Native SB mid-flow peek-lock/complete: Egress Azure Service Bus; trigger ADR 0015 option C