In the previous section, we used composer to pull in Guzzle, so we're ready to use it in our project. However, we'd rather not have to instantiate the Guzzle client manually every time we invoke it—hardcoding URLs and authentication and settings with each use. A service provider can help to centralize some of this configuration, and later, we will use service providers to help swap in a mock implementation for testing purposes.
Providers can also help us to avoid writing code that directly calls to a service, which is often a very helpful practice. For example, we may make BillingProvider that can use either Swipe or BrightTree as a billing service. BillingProvider allows us to easily switch between different implementations of the billing service.
Follow the steps in the Working with Composer install command and avoiding composer update section to pull in Guzzle, and start up your terminal.
