Guzzle

Overview Laravel continues to refine its developer experience with the release of versions 12.32 and 12.33. These updates introduce more than just syntactic sugar; they provide robust tools for handling complex asynchronous workflows and database reliability. The standout feature is a new `Http::batch` method, bringing the same power we see in job batching directly to external API interactions. Prerequisites To follow along, you should have a solid grasp of PHP type hinting and Laravel's service container. Familiarity with Guzzle or the standard Laravel HTTP Client is essential, as these features build upon existing networking patterns. Key Libraries & Tools - **Laravel HTTP Client**: The core service for fluent API requests. - **Fluent Strings**: A set of methods for object-oriented string manipulation. - **Database Transactions**: The system that ensures data integrity through rollbacks. HTTP Batching and Lifecycle Hooks While the `pool` method allows for simultaneous requests, the new `batch` method introduces a managed lifecycle. This is a massive improvement for developers interacting with multiple third-party services. You can now define logic based on the success or failure of the entire collection of requests. ```php Http::batch(function ($batch) { return [ Http::async()->get('https://api.example.com/user'), Http::async()->get('https://api.example.com/posts'), ]; })->before(function () { // Initialize resources })->then(function ($responses) { // All succeeded })->catch(function ($exception) { // Handle failure })->finally(function () { // Clean up }); ``` Transaction Safety with AfterRollback Handling side effects when a database transaction fails has historically been tricky. The new `afterRollback` event support allows you to trigger specific logic—like logging an error to an external monitoring tool or clearing a temporary cache—only when a transaction fails to commit. This prevents your application from being in an inconsistent state where the database reverted but your external systems acted as if it succeeded. Syntax Notes - **Doesn't Contain**: The `Stringable` class now includes `doesntContain()`, removing the need for `!str()->contains()`. This results in more readable, prose-like code. - **Param Merging**: The HTTP client now merges URL parameters by default instead of overriding them, simplifying how we build dynamic queries. Tips & Gotchas Always remember that `Http::batch` relies on asynchronous execution. If you forget to use `Http::async()` inside the batch callback, you won't reap the performance benefits of parallel execution. For debugging, use the `catch` hook to dump the specific response error; this is often more descriptive than a generic exception message.