Use at-least-once plus idempotence to build self-healing systems

The one-slide takeaway of the talk: if you remember only one thing, use the recipe 'at-least-once + idempotence' at every component boundary. It is not a silver bullet, but it enables systems to resume communication after problems, take care of their workflows, and self-heal once the underlying issue is gone — dramatically reducing production babysitting.