Overview

Newline’s Message Queue (MQ) system provides a robust, pull-based mechanism for delivering real-time event notifications. It is designed for clients who require durable, fault-tolerant message delivery and have infrastructure to support queue-based consumption.

What Is the Message Queue?

The MQ allows clients to subscribe to specific event topics and consume messages using protocols like STOMP, AMQP, MQTT, and WSS. Unlike Webhooks, MQ does not push messages to endpoints—instead, clients connect to the broker and pull messages as needed.

MQ is built on Apache ActiveMQ and AWS MQ, offering flexibility and reliability for high-volume, asynchronous event processing.

Key Features

Durable Subscriptions: Messages are retained even if the client disconnects.
Protocol Flexibility: Supports multiple messaging protocols.
Fault Tolerance: Clients can resume consumption without losing messages.
Topic-Level Control: Subscribe to specific topics or event types.

Getting Started

To begin using MQ, follow these steps:

Review Authentication Requirements Learn how to securely connect to the MQ broker using provided credentials. For more information visit MQ Authentication.
Understand Available Topics Explore the list of supported topics and their naming conventions. For more information visit MQ Topics.
Review Topic Definitions Get detailed descriptions of each topic and the events they include. For more information visit MQ Topic Definitions.
Learn About Topic Publication Understand how Newline publishes messages to topics and how naming schemes work. For more information visit MQ Topic Publication.
Set Up Subscriptions Follow the steps to register and manage durable subscriptions. For more information visit MQ Subscriptions

Best Practices

Use durable subscriptions with unique IDs.
Implement idempotency using event IDs.
Monitor connection health and retry logic.
Test thoroughly in sandbox before going live.