Very interesting. I’ll keep an eye on this as a way to factor out common patterns from service bindings. It’s frustrating that many service bindings implement retries/logging/etc in an ad-hoc way and a good common idiom for that would help.
By the way, (&) is the conventional name for the (|>) operator. I’ve written an earlier explanation about why, but it came first and has much better consistency with the rest of the visual language of Haskell operators.