> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/inter-service-communication/messaging-communication/activemq/naming-convention.md). # Naming Convention ## About In ActiveMQ, consistent and descriptive naming conventions are critical for managing message destinations, especially when using features like **Virtual Topics**, **Dead Letter Queues**, and **multiple consumer groups** in a microservices architecture. ## **Traditional Queue (Producer Side)** ``` queue:// ``` * **What it means**: The producer sends a message to a single, named queue. * **Message flow**: One message goes to one queue. * The broker will deliver the message to **one available consumer**. **Example** ``` jms_destination = queue://order-processing ``` * A producer sends order-related messages to the queue named `order-processing`. ## **Traditional Queue (Consumer Side)** Consumers listen to the **same** queue name: ``` queue:// ``` * Each consumer will **compete** for incoming messages. * Only **one** consumer will receive any given message. * This is used for **load-balanced message processing** among multiple instances of the same service. **Example** ``` jms_destination = queue://order-processing ``` * Service A has **three instances (pods)** listening to `order-processing`. * Messages are load-balanced — each pod gets different messages. ## **Virtual Topic (Publisher-Side Topic)** ``` topic://VirtualTopic. ``` * This is the topic where the **producer** sends messages. * Each message sent here is duplicated into queues for any subscribed consumers using the matching `queue://Consumer.X.VirtualTopic.` format. **Example:** ``` topic://VirtualTopic.notifications ``` * Sent messages are fanned out to: * `queue://Consumer.A.VirtualTopic.notifications` * `queue://Consumer.B.VirtualTopic.notifications` * `queue://Consumer.C.VirtualTopic.notifications` * ... etc. Each of these queues is **isolated**. One consumer group does **not interfere** with others. ## **Queue Destination (Virtual Topic Consumer Queue)** ``` queue://Consumer..VirtualTopic. ``` **Components Breakdown:**

Part	Description
`queue://`	Specifies the protocol and that the destination is a queue (not a topic).
`Consumer`	Prefix to indicate that this queue is a consumer-side queue for a virtual topic.
`<ConsumerGroup>`	Logical group name of the microservice or consumer. Used to create isolated queues for each group.
`VirtualTopic`	Fixed keyword required to work with Virtual Topics.
`<TopicName>`	The name of the virtual topic being subscribed to.

**Example:** ``` jms_destination = queue://Consumer.B.VirtualTopic.notifications ``` This means: * Messages were originally published to:\ `topic://VirtualTopic.notifications` * ActiveMQ **automatically created a copy** of the message in a queue:\ `queue://Consumer.B.VirtualTopic.notifications` * This queue is **private to consumer group B**, allowing it to process messages independently from other consumers. ## **Dead Letter Queue (DLQ)** Messages that cannot be processed successfully are sent to the Dead Letter Queue. ``` queue://ActiveMQ.DLQ ``` * Default DLQ for ActiveMQ. * Can be customized using broker configuration. * Helps in debugging failed message deliveries. ## **Naming in Microservices Context** In microservices, multiple instances (pods) of the same service may consume from the same queue. The naming convention ensures: * Messages are not duplicated between services. * Each service or bounded context receives its **own copy** of the message (if using Virtual Topics). * Load balancing happens within the group, not across groups. #### Example Use Case **Producer:** ``` jms_destination = topic://VirtualTopic.user.events ``` **Consumers:** ``` queue://Consumer.audit.VirtualTopic.user.events queue://Consumer.notification.VirtualTopic.user.events queue://Consumer.analytics.VirtualTopic.user.events ``` * `audit`, `notification`, and `analytics` services all get the **same message**, but in their own isolated queues. * Each service can independently scale with multiple pods consuming messages from their respective queues. ## **Best Practices for Naming**

Best Practice	Reason
Use descriptive consumer group names (e.g., `Consumer.NotificationsService`)	Helps trace ownership and intent
Keep topic names generic (e.g., `VirtualTopic.user.events`)	Allows reuse across services
Avoid hardcoding destination names in code	Use environment variables or configuration files
Prefix DLQs with service name (e.g., `DLQ.NotificationsService`)	Easier to manage failures per service
Use lowercase and hyphens or dots for topic/queue names	Improves readability and consistency

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/inter-service-communication/messaging-communication/activemq/naming-convention.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.