Memento pattern realworld example

[drissboumlik]

No description provided.

[neochief]

Hi Driss!

Thanks for the example. To be honest with you, I hardly see the point of having such an order history class in place (why do you ever revert the order state?). I've been working with lots of ordering/payments systems, none of them had anything like this.

In my opinion, a good example for this pattern should play around these two scenarios:

1. The memento must have sensitive info (so that the problem would be not letting caretaker access that info)
2. OR there should be too many types of various mementos (so that the problem would be not making caretaker depend on dozens specific types of mementos).

A feature of a good example is also that the reader doesn't think "why do you have to have all this classes and not just two arrays". This is super hard thing to achieve with the real world examples, ha-ha.

Let me know what you think.

[drissboumlik]

hmm, I see
what about a shopping cart abandonment & recovery (saving cart states so users can return later to complete purchases)
or an admin dashboard where users can update the site configuration, the system should allow rollbacks.

[neochief]

Man, site config with the ability to rollback is very promising idea!

[drissboumlik]

something like this :

// Originator
class ConfigManager { }

// The Memento interface
interface ConfigMemento {}

// The Concrete Memento
class ConfigSnapshot implements ConfigMemento {}

class ConfigHistory {}

// ....
$config = new ConfigManager([
    'maintenance_mode' => false,
    'theme' => 'light',
    'seo' => ['title' => 'My Website', 'description' => 'Welcome to my site!'],
    'debug' => false,
    'max_users' => 1000
]);