Expand description
Facilities to consume messages from a RabbitMq queue. Check out ConsumerGroup as a
starting point.
Modules§
- hooks
- A collection of ready-made hooks for the most common use cases.
Structs§
- Consumer
Group - A collection of RabbitMq consumers sharing the same context and connection settings.
- Consumer
Group Builder - A builder to register message handlers once the group-level configuration of a
ConsumerGrouphas been finalised. - Consumer
Group Configuration Builder - A builder for group-level configuration of a
ConsumerGroup. - Delivery
- A received AMQP message.
- Handler
Error - The error type returned by message handlers.
- Incoming
- A dequeued message enriched with some auxiliary data, ready for processing.
- Message
Handler - A handler processing messages from a RabbitMq queue.
- Message
Handler Builder - A builder to compose a
MessageHandlerwith a fluent API. - Message
Processing - The remainder of the middleware chain (telemetry + processing), including the final message handler.
- Next
- The remainder of the processing middleware chain, including the final message handler.
- Processing
Outcome - The outcome of message processing:
Enums§
- Broker
Action - The action we asked the broker to take when finalising the processing of the current message.
- Error
Type - Types of failure when handling a message. Used by the pub sub framework to handle retries/nacks/dead letter queues/etc.
- Processing
Error - Should
Requeue - Determines if a failed message should be re-queued.
Traits§
- Consumer
PreStart Hook - A hook to execute logic before a
MessageHandlerstarts processing messages. - Consumer
Transient Error Hook - A hook to determine if failed messages due to a transient error should be requeued.
- Handler
- Implementers of the
Handlertrait can be used in our RabbitMqMessageHandlers to process messages retrieved from a queue. - Processing
Middleware - Middlewares to execute logic before and after the message handler function.
- Telemetry
Middleware - Middlewares to collect and emit telemetry data based on the outcome of message processing.
Functions§
- get_
message_ local_ item - Retrieve an item from message-local storage based on its type.
- set_
message_ local_ item - Insert an item in message-local storage. If another item with the same type was already stored in message-local storage it gets replaced.