You Don't Always Need a Workflow Engine to Roll Back a Failed Checkout
Here's a sequence that shows up in almost every Laravel app that talks to the outside world: Charge the customer's card. Create a policy (or order, or booking) with a partner API. Generate a PDF confirmation. Step 3 throws. Maybe the PDF library ran out of memory, maybe the storage disk is full. Whatever the reason, you're now sitting on a charged card and a partner-side record that your own…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.
