Memento Design Pattern (C#) 

Love it. Would like a description of what it is before I watch. The memento pattern is a software design pattern that provides the ability to restore an object to its previous state (undo via rollback). The memento pattern is implemented with three objects: the originator, a caretaker and a memento.

That's really helpful, thank you. I'll use it at my job. I need to implement a rollback but I'm unable to do a Saga, because the two services I'm calling in order to update an object don't have event listeners and one of them will be deprecated soon, so implementation of handlers is not an option. I need to be able to rollback the previous state in order to send a second update request. I use Redis to store the previous state, but this is a more elegant way. Thank you!

best channel you could find

marvellous explanations bro... really appreciate and very helpful. Would you please start Apache Kafka tutorials also... 🙂

🎉

Hi buddy, keep up the hard work! 👍

I don't see why using Editor and Snapshot (EditorState) classes are helpful. If we want to add or undo changes, then why not have a History class to store the state history in a Stack or a List? Why bring up other classes like Editor class or Snapshot class? public class History { private Stack states = new Stack(); public void push(T item) { states.push(); } public T pop() { return states.pop(); } }

Man amazing!! I didn't know that if you accept another object A of the same class as you (A), you can reference it's private field!! I guess you would know it's address in memory?? How does this work, I'm perplexed!

👍🏽