How does Laravel's service container and service providers work together to manage dependency injection and bootstrap an application's various services?

Laravel's service container automatically resolves and injects a class's dependencies based on type hints, as with any dependency injection container, while service providers are the central place where an application registers bindings into that container and performs any necessary bootstrapping logic, such as registering event listeners or publishing configuration files, meaning nearly every significant piece of functionality within Laravel, including many of the framework's own core features, is wired together through this consistent service provider pattern.

class PaymentServiceProvider extends ServiceProvider {
    public function register() {
        $this->app->bind(PaymentGateway::class, StripeGateway::class);
    }
}