Can you explain the Dependency Inversion Principle and its importance in software development?

The Dependency Inversion Principle (DIP) is one of the five SOLID principles, which states that:

1. High-level modules should not depend on low-level modules. Both should depend on abstractions.
2. Abstractions should not depend on details. Details should depend on abstractions.

This means that instead of a class directly creating or using specific implementations of other classes, it should work with abstractions (such as interfaces or abstract classes). This increases flexibility, makes testing easier, and supports code maintenance.

Example in PHP:

interface LoggerInterface {
    public function log(string $message);
}

class FileLogger implements LoggerInterface {
    public function log(string $message) {
        // write to file
    }
}

class UserService {
    private $logger;

    public function __construct(LoggerInterface $logger) {
        $this->logger = $logger;
    }

    public function createUser($userData) {
        // user creation logic
        $this->logger->log('User created');
    }
}

Now, UserService depends on the abstraction LoggerInterface, not on the concrete implementation FileLogger.

This simplifies replacing the logger, for example, with a database logger, without changing UserService.