Skip to content
28th October 2026Wolverine Best Practices, RevisitedThe Wolverine Best Practices guide was written in 2023 and pointed at a handful of blog posts from that year. We've rewritten it from scratch: the A-Frame Architecture front and center, concrete advice on dividing handlers and error handling by category, the at-least-once rules every messaging community agrees on, and links to the tutorials that didn't exist back then.14th October 2026Broadcasting to Every Node with WolverineMost messaging is about one node handling each message, but sometimes every node needs a copy. Here's how to do that with NATS in a Wolverine application, the new BroadcastToAllNodesAsync() in Wolverine 6.50 that works on any transport, how it fits with Wolverine's SignalR support, and what your options are with Rabbit MQ and the other brokers.29th September 2026The F5 Experience, Even with Rabbit MQ, AWS SQS, or Azure Service BusA fresh git clone, docker compose up -d, and F5. That's the whole onboarding story for a Critter Stack application, and with Wolverine's AutoProvision() it stays that way when you add asynchronous messaging through Rabbit MQ, Amazon SQS, or Azure Service Bus. Here's how the stateful resource model, the resources command, and environment checks make that work.20th September 2026Yes, You Can Have Ordered Messaging in a ClusterPlenty of .NET messaging tools tell you that ordered processing isn't possible once you scale out. Wolverine gives you a whole range of options, from exclusive single-node listeners to strictly ordered queues to cluster-wide global partitioning, with failover built in.15th September 2026Wolverine's Production-Capable In-Memory QueuesWolverine's local queues give modular monoliths in-process messaging that's backed by the transactional inbox, durable against process crashes, fully instrumented with OpenTelemetry and metrics, and tunable for sequencing, partitioning, and circuit breaking. Here's why that makes them a much better fit than MediatR notifications.3rd September 2026LLM Callouts in WolverineWolverineFx.AI adds LLM callouts to Wolverine — one-shot calls to a large language model modeled as ordinary messages, so they get the transactional outbox, retries, back pressure, budgets, and testability for free. The first thing JasperFx is building on it is AI Assisted Production Support in CritterWatch 1.1.24th August 2026Wolverine is the Undisputed Champion of Low Ceremony CodeNServiceBus and MassTransit have both shipped welcome improvements to their message handler ergonomics. Let's give credit where it's due, then walk through why Wolverine's approach to low ceremony code — no mandatory anything, inlined dependencies, pure function handlers, cascading messages, and readable generated code — is still in a class of its own.4th August 2026One Application, Many Brokers: Wolverine's Multi-Transport and Broker-per-Tenant StoryReal systems rarely get to standardize on one message broker. Wolverine lets a single application speak Rabbit MQ, Azure Service Bus, Kafka, and MQTT at once — and takes it one step further with a broker-per-tenant model where the tenant id is inferred from the connection a message arrived on and carried all the way into the database transaction.17th July 2026Ordered Messaging Without the Locks: Wolverine's Global Partitioning and Re-SequencerStrict message ordering usually means single-threaded consumers, distributed locks, or a lot of hand-rolled bookkeeping. Wolverine's global partitioning and re-sequencer give you ordered processing across a cluster while still scaling out — no explicit locking required.
Messaging
Posts tagged Messaging
28th October 2026Wolverine Best Practices, RevisitedThe Wolverine Best Practices guide was written in 2023 and pointed at a handful of blog posts from that year. We've rewritten it from scratch: the A-Frame Architecture front and center, concrete advice on dividing handlers and error handling by category, the at-least-once rules every messaging community agrees on, and links to the tutorials that didn't exist back then.14th October 2026Broadcasting to Every Node with WolverineMost messaging is about one node handling each message, but sometimes every node needs a copy. Here's how to do that with NATS in a Wolverine application, the new BroadcastToAllNodesAsync() in Wolverine 6.50 that works on any transport, how it fits with Wolverine's SignalR support, and what your options are with Rabbit MQ and the other brokers.29th September 2026The F5 Experience, Even with Rabbit MQ, AWS SQS, or Azure Service BusA fresh git clone, docker compose up -d, and F5. That's the whole onboarding story for a Critter Stack application, and with Wolverine's AutoProvision() it stays that way when you add asynchronous messaging through Rabbit MQ, Amazon SQS, or Azure Service Bus. Here's how the stateful resource model, the resources command, and environment checks make that work.20th September 2026Yes, You Can Have Ordered Messaging in a ClusterPlenty of .NET messaging tools tell you that ordered processing isn't possible once you scale out. Wolverine gives you a whole range of options, from exclusive single-node listeners to strictly ordered queues to cluster-wide global partitioning, with failover built in.15th September 2026Wolverine's Production-Capable In-Memory QueuesWolverine's local queues give modular monoliths in-process messaging that's backed by the transactional inbox, durable against process crashes, fully instrumented with OpenTelemetry and metrics, and tunable for sequencing, partitioning, and circuit breaking. Here's why that makes them a much better fit than MediatR notifications.3rd September 2026LLM Callouts in WolverineWolverineFx.AI adds LLM callouts to Wolverine — one-shot calls to a large language model modeled as ordinary messages, so they get the transactional outbox, retries, back pressure, budgets, and testability for free. The first thing JasperFx is building on it is AI Assisted Production Support in CritterWatch 1.1.24th August 2026Wolverine is the Undisputed Champion of Low Ceremony CodeNServiceBus and MassTransit have both shipped welcome improvements to their message handler ergonomics. Let's give credit where it's due, then walk through why Wolverine's approach to low ceremony code — no mandatory anything, inlined dependencies, pure function handlers, cascading messages, and readable generated code — is still in a class of its own.4th August 2026One Application, Many Brokers: Wolverine's Multi-Transport and Broker-per-Tenant StoryReal systems rarely get to standardize on one message broker. Wolverine lets a single application speak Rabbit MQ, Azure Service Bus, Kafka, and MQTT at once — and takes it one step further with a broker-per-tenant model where the tenant id is inferred from the connection a message arrived on and carried all the way into the database transaction.17th July 2026Ordered Messaging Without the Locks: Wolverine's Global Partitioning and Re-SequencerStrict message ordering usually means single-threaded consumers, distributed locks, or a lot of hand-rolled bookkeeping. Wolverine's global partitioning and re-sequencer give you ordered processing across a cluster while still scaling out — no explicit locking required.