Behavioral Patterns - Memento Pattern Exercise

behavioral-patterns-memento-pattern-exercise

The Memento Pattern is used to record the internal state of an object. It is used to create a state machine and also makes undo or redo operation very easy with this pattern. In this exercise, we will use a scenario of account and account manager to understand the components of this pattern.

Reading Materials

  1. https://en.wikipedia.org/wiki/Memento_pattern (15 minutes reading)

Practice Materials

  1. Use the Memento Pattern to support an account manager to do save and roll back operations for his managed accounts.

Components:

  1. Originator (The object whose state will be saved as a memento) - Account
  2. Memento (The object that represent the saved state from its originator) - AccountMemento
  3. Caretaker (The object that keep the immutable state of mementos) - AccountManager
  4. Client (The entry point of the application that will run the given scenario) - App

Tip

  • Not all states of the originator have to be saved to a memento object.
  • To implement rollback or revert in the AccountManager, a stack could be used to keep track of the entire memento history.
  • Account.deposit or Account.withdraw could be created to change the Account.balance

Solution

Account Manager Example

Questions to discuss

  1. What are the common use cases to apply a Memento Pattern?
  2. What are the similarities and differences of the Memento Pattern and the Command Pattern?

Comments

Post a Comment

Popular posts from this blog

Distributed Transaction Management with REST and Try Confirm/Cancel Pattern

distributed-transaction-management-with-rest-and-try-confirm-cancel-patternThis article introduces how to manage transactions effectively in distributed REST services with Try Confirm/Cancel (TCC) pattern. It also provides a repository that is a simplified Java implementation for anyone who is interested in learning the TCC pattern. This repository attempts to trim the most of the common boilerplate, but only preserve the minimal that could be most straightforward to observe this pattern. It could be adapted to use any backend stack.Try Confirm/Cancel (TCC) PatternTCC is a distributed transactions pattern that fits in the stateless REST services. It is originally proposed by Guy Pardon, the creator of Atomikos.Useful ReferencesConference Speech By Guy PardonTCC for REST API (API specification)Spring Cloud TCC Example By ChrisAbout This RepositoryThis repository is a simplified Java implementation for anyone who is interested in learning the TCC pattern. This repo attempts to trim the …
Read more

Spring JMS and JPA XA Transactions with WebLogic

spring-jms-and-jpa-xa-transactions-with-weblogicThis article shows the configuration of using XA transactions with the resources managed by WebLogic server.There are three parts of configurations for this XA transactions to work - JMS, JPA and JTA. Both JMS and JPA are acquired through the JNDI registry and the XA transaction manager implementation uses the one from the WebLogic server. This configuration relies on WebLogic server. The concept should be similar and applicable to other JEE application servers. With these configurations, we could easily use @Transactional annotation on the services for XA transactions.JmsConfiguration.java Excerpt@ConfigurationpublicclassJmsConfiguration{// properties...@Beanpublic ConnectionFactory connectionFactory(){returnlookupByJndiTemplate(jmsConnectionFactory, ConnectionFactory.class);}@Beanpublic JndiTemplate jndiTemplate(){ JndiTemplate jndiTemplate =newJndiTemplate(); jndiTemplate.setEnvironment(getJndiProperties());return jndi…
Read more

Spring Data MongoDB GridFS 3.4

spring-data-mongodb-gridfs-3-4This article shows a typical usage of MongoDB GridFS with Spring Data MongoDB. This is for MongoDB java driver v3.4 and Spring Data MongoDB v1.10.x. Note that Spring Data MongoDB v2.X introduces breaking changes with the MongoDB java driver 3.6+. This article only shows the usage of the v3.4 driver with Spring Data MongoDB v1.10.x.FileService InterfacepublicinterfaceFileService{ GridFSDBFile find(String id); Optional<GridFsResource>findAsResource(String id); String store(String name, MultipartFile file);voiddelete(String id);}FileService ImplementationWe can’t use GridFsTemplate.getResource(String location) here to get the resource because there might be files with the same name. To find the expected file, we need to find a list of the resources that all match the same filename and then filter them by the id after retrieving all the files. This is acceptable because at that point, the InputStream hasn’t been requested yet. GridFsTemplate…
Read more