Choosing and verifying a Wolverine endpoint mode Added in 1.7.0
Choose and verify a Wolverine listener endpoint mode — Inline, BufferedInMemory, Durable, and NativeAck — across all three axes that matter: delivery guarantee, per-message database cost, and how long the broker holds a delivery unsettled while your handler runs. Covers the mode matrix, how to set each mode, why group partitioning is a separate opt-in call rather than a property of any mode, and why local ordering calls (Sequential, PartitionProcessingByGroupId) do not order a cluster — that needs ListenWithStrictOrdering or MessagePartitioning.GlobalPartitioned, when NativeAck is the right answer (and when it is not), how to assert the mode you configured is the one you actually got, and the silent concurrent-duplicate failure that long-running handlers hit on clocked transports.
Use when configuring listeners, tuning throughput, diagnosing duplicate or lost messages, or answering 'which endpoint mode should I use?'
Skill details
- Skill name:
wolverine-messaging-endpoint-modes - Applies to:
wolverine - Tags:
messaging,endpoints,listeners,throughput,delivery-guarantees,native-ack,durability,transports - Added in: 1.7.0
- License: Proprietary. Copyright JasperFx Software LLC.