microservices

Name: microservices
Availability: InStock
Author: mthang1801

Configure RabbitMQ or Kafka brokers and shared patterns for NestJS microservices.

Updated Aug 27, 2026

Search Tags:#messaging #microservices #registry #kafka #nestjs #rabbitmq #subscribe-pattern

Ready to run

npx skills add https://github.com/mthang1801/go-domain-driven-design --skill microservices-mthang1801

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microservices
Source: https://github.com/mthang1801/go-domain-driven-design/tree/main/.claude/skills/microservices
Command: npx skills add https://github.com/mthang1801/go-domain-driven-design --skill microservices-mthang1801

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures message broker configurations and shared patterns across microservices to enable reliable publish/subscribe flows.

Core Features & Use Cases

Centralized broker configuration
Decorator-based subscription (SubscribeEventPattern/SubscribeMessagePattern)
Registry-driven client initialization and consumer startup
Real-world examples across loan-product and dynamic-form services

Quick Start

Define shared broker configs, register clients, initialize consumers, and run both publisher and subscriber services.

Frequently Asked Questions about microservices

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

FAQPage Schema

How do I configure RabbitMQ and Kafka brokers for NestJS microservices?▼

To configure RabbitMQ and Kafka brokers for NestJS microservices, you define centralized broker configurations and register modules to initialize clients and consumers with matching subscribe patterns. This enables reliable publish/subscribe flows.

What is the subscribe pattern for microservices message brokers?▼

The subscribe pattern for microservices uses decorator-based declarations like SubscribeEventPattern and SubscribeMessagePattern to match publishers and consumers. Registry-driven initialization starts consumers automatically based on these declared patterns.

How do I set up publish/subscribe flows across multiple NestJS services?▼

You set up publish/subscribe flows across NestJS services by defining shared broker configs, registering clients, and initializing consumers with matching Subscribe patterns. Real-world examples include loan-product and dynamic-form services.

Can I use both RabbitMQ and Kafka in the same microservices architecture?▼

Yes, you can use both RabbitMQ and Kafka in the same microservices architecture. This approach provides centralized broker configuration and registry-driven client initialization to support consistent publish/subscribe messaging across different brokers.

What's the best way to standardize event patterns across microservices?▼

The best way to standardize event patterns across microservices is using decorator-based subscriptions like SubscribeEventPattern and SubscribeMessagePattern. This registry-driven approach ensures consistent pattern matching and reliable consumer initialization.

Does this microservices configuration require any external dependencies?▼

No, this microservices configuration requires no external dependencies. It provides references for declaring broker configs, registering modules, and initializing consumers entirely within your NestJS-based services.