Skip to content
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.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.
RabbitMQ
Posts tagged RabbitMQ
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.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.