How can the Decorator pattern be used to address the issue of mixing logic and persistence in PHP?

Issue: Mixing logic and persistence in PHP can lead to code that is difficult to maintain, test, and extend. To address this issue, the Decorator pattern can be used to separate the concerns of business logic and persistence, allowing for better organization and flexibility in the codebase. 

<?php

// Interface for the base component
interface ComponentInterface {
    public function operation(): string;
}

// Concrete component implementing the ComponentInterface
class ConcreteComponent implements ComponentInterface {
    public function operation(): string {
        return "Executing operation in ConcreteComponent";
    }
}

// Decorator class implementing the ComponentInterface
abstract class Decorator implements ComponentInterface {
    protected $component;

    public function __construct(ComponentInterface $component) {
        $this->component = $component;
    }

    public function operation(): string {
        return $this->component->operation();
    }
}

// Concrete decorator adding persistence functionality
class PersistenceDecorator extends Decorator {
    public function operation(): string {
        $result = parent::operation();
        // Add persistence logic here
        return $result . " with persistence";
    }
}

// Usage
$component = new ConcreteComponent();
$decoratedComponent = new PersistenceDecorator($component);
echo $decoratedComponent->operation();

?>

Keywords

Decorator pattern logic persistence PHP mixing

Related Questions