wolverine-azure-service-bus

Manage cross-service domain events in CritterCab using Azure Service Bus.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-azure-service-bus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wolverine-azure-service-bus
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/wolverine-azure-service-bus
Command: npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-azure-service-bus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Aspire.Hosting.Azure.ServiceBus, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage and route cross-service domain events in CritterCab using Azure Service Bus, ensuring reliable message delivery and processing across bounded contexts.

Core Features & Use Cases

  • Domain Event Routing: Publish and subscribe to domain events with reliability and scalability.
  • Topic and Subscription Management: Configure topics and subscriptions for fan-out and point-to-point messaging.
  • Dead-letter Queues: Handle message failures with native dead-letter queues and custom Wolverine routing.
  • Use Case: In a ride-sharing platform, this Skill can be used to route TripCompleted events to various services like Payments, Ratings, and Operations.

Quick Start

Configure the Skill to publish TripCompleted events to the 'trips.trip-completed' topic in Azure Service Bus.

Frequently Asked Questions about wolverine-azure-service-bus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route domain events across microservices using Azure Service Bus?

Domain event routing with Azure Service Bus uses topics and subscriptions to publish and subscribe to messages, ensuring reliable event distribution across bounded contexts. This Skill configures that routing natively within Wolverine.

What is the best way to handle failed messages in an event-driven architecture with Azure Service Bus?

Handling failed messages in Azure Service Bus is best done using native dead-letter queues combined with custom Wolverine routing. This approach captures message failures safely for inspection and retries within complex workflows.

Does this Skill require Aspire for Azure Service Bus configuration?

Yes, this Skill requires the Aspire.Hosting.Azure.ServiceBus dependency to manage the hosting and provisioning of Service Bus resources. You need this environment setup to configure topics and subscriptions correctly.

How do I configure fan-out messaging for a ride-sharing platform in Azure Service Bus?

Fan-out messaging in Azure Service Bus is configured by creating a single topic with multiple subscriptions. Services like Payments and Ratings each subscribe to the same topic to receive copies of events like TripCompleted.

When do I need dead-letter queues for message queuing in microservices?

You need dead-letter queues for message queuing when processing complex workflows where messages might fail or expire. They store undeliverable events safely, preventing data loss in your event-driven architecture.

Can I use Wolverine for cross-service domain event distribution?

Yes, you can use Wolverine for cross-service domain event distribution by configuring it with Azure Service Bus. It enables reliable message delivery and custom routing across different bounded contexts and microservices.