Aj.RabbitMQ.Core 1.0.54

Aj.RabbitMQ.Core

🚀 Biblioteca .NET para abstração de mensageria no RabbitMQ, totalmente extensível, orientada a microsserviços e multi-tenant.

✨ Recursos

✅ Conexão centralizada (singleton)
✅ Configuração via IConfiguration e DataAnnotations
✅ Declaração de exchanges, filas, bindings padronizados
✅ Suporte a prefetch (QoS)
✅ Envelope de mensagens estruturado (MessageEnvelope)
✅ Retry e DLQ integrado (padrão de robustez)
✅ Helpers para exchanges direct, topic, fanout
✅ Extensões para injeção no IServiceCollection

📦 Instalação

no seu projeto:

dotnet add package Aj.RabbitMQ.Core

⚙️ Configuração

adicione ao seu appsettings.json:

"RabbitMQSettings": {
  "HostName": "localhost",
  "UserName": "admin",
  "Password": "123456",
  "VirtualHost": "/",
  "Port": 5672,
  "RoutingKey": "order.vtex"
}

OBS: A Propriedade "RoutingKey" so deve ser informada para definir em qual fila os consumers devem se conectar, caso o serviço seja um publisher manter como null e definir a routingkey no momento da publicação.

e registre no Program.cs:

builder.Services.AddRabbitMQServices(builder.Configuration);

🚀 Uso Básico

var connectionFactory = serviceProvider.GetRequiredService<RabbitMQConnectionFactory>();
var channel = await connectionFactory.GetChannelAsync();

Envelope worker vs Outbox worker

Aj.RabbitMQ.Core ships two consumer families:

Use envelope workers for legacy integrations that publish wrapped envelopes. Use outbox workers for messages published by the Outbox Poller (flat camelCase JSON on a named queue).

Outbox worker example

public sealed class OrderWorker : RabbitMQOutboxWorker<PayloadContent>
{
    public OrderWorker(IConfiguration config)
        : base(config, "order.integrations.abacos") { }

    protected override Task<EnvelopeStatus> HandleMessageAsync(
        PayloadContent message,
        CancellationToken cancellationToken) => ...;
}

Configure queue binding explicitly when needed:

public sealed class CustomOrderWorker : RabbitMQOutboxWorker<PayloadContent>
{
    public CustomOrderWorker(IConfiguration config)
        : base(config, new RabbitConsumerBinding
        {
            QueueName = "order.integrations.abacos",
            PrefetchCount = 5,
            DeclareQueueOnStartup = true
        }) { }

    protected override Task<EnvelopeStatus> HandleMessageAsync(
        PayloadContent message,
        CancellationToken cancellationToken) => ...;
}

Outbox delayed retry (opt-in)

Legacy outbox workers keep immediate BasicNack(requeue: true). For catalog queue names with a {queue}.retry sister queue (TTL → dead-letter back to main), set RetryMode = RabbitRetryMode.RetryQueue on the binding. Declare topology from the Outbox Poller with EnsureRetryTopologyOnPublish or DeclareQueueOnStartup = true on the binding.

: base(config, new RabbitConsumerBinding
{
    QueueName = "order.integrations.abacos",
    RetryMode = RabbitRetryMode.RetryQueue,
    DeclareQueueOnStartup = true
})

🟦 Retry + DLQ

por padrão, sugerimos:

• fila normal
• fila .retry com x-message-ttl
• fila .dlq para mensagens definitivas
• exchanges:
  • direct.order
  • direct.retry
  • direct.dlq

📚 Exemplos avançados

declarar exchange

await _channel.ExchangeDeclareAsync(
    exchange: "direct.order",
    type: "direct",
    durable: true,
    autoDelete: false
);

declarar fila com TTL + DLQ

await _channel.QueueDeclareAsync(
    queue: "order.billing.retry",
    durable: true,
    exclusive: false,
    autoDelete: false,
    arguments: new Dictionary<string, object>
    {
        { "x-message-ttl", 300000 },
        { "x-dead-letter-exchange", "direct.order" },
        { "x-dead-letter-routing-key", "order.created" }
    }
);

✅ Checklist de Qualidade

• Multi-tenant
• Extensível
• Segue princípios SOLID
• Fácil integração com MediatR e Polly
• Suporte ao plugin management do RabbitMQ

👨‍💻 Contribuições

Pull Requests são muito bem-vindos!
Basta abrir uma issue ou PR neste repositório.

📄 Licença

MIT