The Phantom Transaction

This e-commerce order handler performs inventory locking, order creation, and an external payment API call all within a single database transaction. Under load, the connection pool is exhausted because each connection is held for the full duration of the external HTTP call. Worse, if the payment succeeds but the commit fails, the customer is charged while inventory rolls back. Refactor the code to separate the transaction boundary from the external call and handle all failure modes.