Enable mechanisms for confirmed delivery: publisher confirms and transactions about amqp HOT 3 CLOSED

This library supports publisher confirms. All you need is to add your buffered chan(s) with http://godoc.org/github.com/streadway/amqp#Channel.NotifyConfirm make sure you're always selecting from them, then put the AMQP Channel into Confirm mode with: http://godoc.org/github.com/streadway/amqp#Channel.Confirm

There is an example here: http://godoc.org/github.com/streadway/amqp#_example_Channel-Confirm Note that this library makes an effort to present a gapless sequence of confirmation numbers so you don't have to handle the batching of sequence numbers the protocol allows. This means that if the server says "I ack until message 9" your NotifyConfirm chan will get 10 messages "0, 1, 2, 3, 4, 5, 6, 7, 8, 9". If the server then says "I ack until message 13", your chan will then get "10, 11, 12, 13".

You can also put the AMQP Channel into transaction mode with http://godoc.org/github.com/streadway/amqp#Channel.Tx But I'm not certain what the server semantics are when using transactions with publisher confirms.

As far as I know, there are no outstanding features missing from the AMQP 0.9.1 spec other than some optional SASL authentication methods.

Also note that this library doesn't present any reconnection/recovery strategies. If a channel errors, then it's best to re-create and redeclare your topology. In most cases, if the library errors, it's best to rebuild the connection.

from amqp.

Cool thanks for the comment and fixing the spec generation issue. I've just gone through a presentation on soundcloud and its use of queues; is this library used in production at soundcloud?

from amqp.

Yes, this library is used in SoundCloud's search indexer and in the data pipeline that drives the Dashboards.

from amqp.