my rabbitmq consumer/producer must never fail!

[dch]

• how can we write rabbitmq producers and consumers that can survive even the zombie apocalypse?
• types of network failures, partitions and how consumers can handle this
• consumer ack choices
• fischer impossibility results & implications for "deliver just once" ideal scenario in bounded time (ref https://decentralizedthoughts.github.io/2019-12-15-asynchrony-uncommitted-lower-bound/ for example)

[dch]

I think looking at this from the client side is an interesting perspective - self-healing resumable examples are what we need in production, but the tutorials are largely conceptual understanding, and the gap is quite large.