Behavioral Patterns - Chain of Responsibility Pattern Exercise

behavioral-patterns-chain-of-responsibility-pattern-exercise

The Chain of Responsibility Pattern is very useful to avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along with the chain until an object handles it. We will implement a naïve security filter chain using this pattern in our practice exercise. You will certainly enjoy this exercise as it is a great way to get you totally master this pattern.

Reading Materials

  1. https://en.wikipedia.org/wiki/Chain-of-responsibility_pattern (15 minutes reading)

Practice Materials

  1. Use chain of responsibility pattern to create a naive security filter chain that will check the following responsibilities in order:
  1. If any endpoint matches the request
  • False - return Not Found
  1. If the endpoint has any security rules
  • False - return Resource
  1. If the request contains any authorization header
  • False - return Unauthorized request
  1. If the authorization is approved
  • False - return Invalid authorization
  1. return Resource

Components

  • Handler (Interface for handling requests)
  • ConcreteHandler (Handle the request it is the responsibility for or forwards it to its successor)
  • Client (Initiate the request to a ConcreteHandler object on any part of the chain, in this example, it should start from the the first filter)

Tips

  • you may create a Helper class to handle some conditional logic

Solution

Naive Security Chain Example

Questions to discuss

  1. What are the common use cases to apply a Chain of Responsibility?
  2. What features are there in the application when you see that you should apply the Chain of Responsibility pattern?

Comments

Post a Comment

Popular posts from this blog

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

Spring Data Repository Query Precedence Tricks

spring-data-repository-query-precedence-tricksSpring Data repository method is very handy but it also comes with its limitation, especially when composed with condition precedence. This article shows one way to work with it and its caveats.Use CaseGiven the following type:@EntitypublicclassBook{@Idprivate Long id;private String title;private String edition;// Getters and Setters ...}1. check if there is any book whose title or edition matches the specified.This one is easy to come up with. We could simply use the keyword Or to compose the query:booleanexistsByTitleOrEdition(String title, String edition);2. check if there is any book whose title or edition matches the specified and is not itself.This one looks just as easy as the first one, we could have just added another condition and compose with the keyword And:booleanexistsByTitleOrEditionAndIdIsNot( String title, String edition, Long id);Is that so?When this method name is translated to SQL, it reads surprisingly astest if an…
Read more

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