It is necessary to modify publish to be synchronous

[lorentz-wu]

The publish function is asynchronous, and after sending, it may not have finished yet. The issue is when the producer should close the connection. It is necessary to modify publish to be synchronous, so that it confirms the message has been sent before returning.

[pmorelli92]

Correct me if I am wrong, but the underlying amqp library does async publishes either way, so there is no way to force that.

https://pkg.go.dev/github.com/rabbitmq/amqp091-go#hdr-Asynchronous_Events
https://pkg.go.dev/github.com/rabbitmq/amqp091-go#Channel.Publish

What I can suggest you is to use the outbox sub module instead, so that the messages are stored in a db table and sent eventually, so no matter if the application stops it will eventually send the message.

https://github.com/pmorelli92/bunnify/tree/main/outbox
https://microservices.io/patterns/data/transactional-outbox.html

[lorentz-wu]

Could you expose the interface for confirming the publish so that I can control and respond to it externally?

[pmorelli92]

Hi @lorentz-wu sorry for the delay. Sure I can add an option or another function for Deferred confirmation, but I would love to hear why do you need this functionality as AMQP is intended for async communication. Wouldn't you be better with a gRPC or HTTP if you want to respond to an event?