Behavioral Patterns - Strategy Pattern Exercise

behavioral-patterns-strategy-pattern-exercise

The Strategy Pattern defines a family of algorithms, encapsulates each one, and makes them interchangeable. Strategy lets the algorithm vary independently from clients that use it. In this exercise, we will use the Strategy Pattern to create a simplified Race model from the popular game World of Warcraft.

Reading Materials

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

Practice Materials

  1. Use the Strategy Pattern to create a Race Model that meets the following requirements:
  • It defines the race traits which varies by each race
  • It has the following two behaviors that could be considered strategies.
    • Dance
    • Fight
  • Implement at least 2 races with different behaviors

Components:

  1. Context (The abstract class that defines the base of all races) - Race
  2. Concrete Context (The implementations of the Race) - Human, Orc, Tauren
  3. Strategy (Different behavior interfaces) - DanceBehavior, FightBehavior.
  4. Concrete Strategy (The interchangeable strategies that could be passed in runtime) - SwingDance, IrishDance, SpellFight, TaichiFight, BoxFight.

Tips

  • If you have never played the World of Warcraft and if you have time and interest in the mid-earth world, it is worth your time.
  • You could find races from the game on the official site

Solution

World of Warcraft Race Model Example

Questions to discuss

  1. What are the common use cases to apply a Strategy Pattern?
  2. What are the OOP design principles used in this exercise?
  • Encapsulate what varies
  • Favor composition over inheritance
  • Program to interfaces, not implementations.

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

Creating a Library Project for Spring Boot

creating-a-library-project-for-spring-bootThis article introduces the key points when creating a library for spring boot project.It could be common that over the years you have created a number of services that could be reused by other spring projects. It then makes sense to make the reusable modules such as a library and install it in your local repository for later use.Here are the key points to consider when building a spring boot library.release versionbuild plugindependency injectionautoconfigurationsRelease VersionTo guarantee spring boot works the way you expect, it is recommended to keep update the release versions of the library so that it supports some versions of the spring boot minor version. A good practice is to monitor change spring boot changelog and see if there are any conflicting dependencies that are used in the library project. If there is, introduce a new version to resolve the conflict.Build PluginIf the projects reference this library doesn’t compile through ma…
Read more