Chain Of Responsability And Builder Pattern

The design patterns are repeatable solutions for commons problem occurring in software design, in this occasion we are going to talk about the Chain Of Responsibility and Builder.

Chain Of Responsibility

The motivation:

This pattern aims on the problem we face at software design when we have several requests and needs to be handling by different object depending on the type of information requested, that turn in plenty of references and instances on the program to make things possible. 

Imagine a candy's coin machine, it doesn't matter what kind of coin you insert inside the slot because it has a chamber or chain of responsibility that check the coins and handle the task must be done by two options, return the coin or the candy, that the same the chain of responsibility do, it handles the request from the client and keep passing through the chain until an object inside could handle it.

Here the diagram of the implementation:


In order to explain the element on this diagram we have:

Customer: this is the class that uses the chain of responsibility.
ChainHandler: Is an abstract class that the chain of responsibility nodes must implement to get the chain workable and become part of it. 
FinanceChainHandler: Is a concreate implementation of the ChainHandler that handle the Finance request inside the chain.
OperationChainHandler: Is a concreate implementation of the ChainHandler that handle the Operation request inside the chain.


Builder

The motivation:

This pattern aims on the problem we face at software design when we have a complex object and leave the responsibility to a builder instead of expose relevant information of instantiation that could turn on a security risk for the whole system.

Imagine you have an API and have a SDK that pass some relevant information you don't want the client handle by his own, for make that possible you'd proceed on creating the object by other object that will handle all those critical aspect for the client thus sending the client the object he needs. Are like a credit card transaction where the payment is the product to be built and the credit card’s network is the black box where the payment is done letting you free about details like: API, network speed, connection point, etc and giving you what you need which is the payment.


Here the diagram of the implementation:


In order to explain the element on this diagram we have:

BuilderConstructor: this is the class handles the objects creation based on the subclass passed to it.
Builder: Is an abstract class having the responsibility of a base class for all builders.
ConcreateBuilder: Is a concreate implementation of the Builder that creates an object of type Item.
Item: is the object we want to create.

Here is the sample code: https://github.com/edgarleonardo/ChainOfResponsabilityAndBuilderPatterns

Regards,



Comments

Post a Comment

Popular posts from this blog

WebSockets Implementation With SignalR And Xamarin.Forms

Image
What is SignalR? ASP.NET SignalR is a .NET framework focus on real-time communications between clients and server, the server can push content instantly to the connected clients when is needed rather than having a server waiting till new client request. so , using SignalR client and server could call method on each other at any time, like image below: (Image Source: https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr) SignalR can be used to add any real-time functionality you want since a chat to any other real-time communication you web or mobile app need and is really easy to use. SignalR, WebSocket  And Transport Falls Back One of the most interesting features of the SignalR Framework is the possibility to support all real time communication supported for the different clients, for example, if one of your client doesn’t support WebSocket then the connection could be made using Long Polling or Server Sent-Event withou...
Read more

Creating A Push Notification Server with ASP.NET And Xamarin.Form App With Firebase Push Notification, Refit, And LiteDB - Part 1 (Firebase Configuration)

Image
This is going to be a series of articles, we are going to explain and develop a single Mobile Application and its respective backend that will handle all operations needed. The application is a proximity geolocation alert application that notifies people close on a defined ration specified by the user who published the issue. The mobile app work for Android and IOS and is developed using Xamarin.Forms. What do we you need to make it possible? Visual Studio 2015 or higher Basic knowledge of C# Google Developer Account Apple Developer Account Basic knowledge of Xamarin.form and cross-platform Let's start! In this first article, we are going to focus on the configuration of our application on the Google Firebase Console. First, we are going to create the set up to be able to use Firebase on our Mobile and ASP.NET Backend API. Login to the Firebase Console (https://console.firebase.google.com/) if you don't have an account yet,  just create a...
Read more

CDN And Cloud Storage On Azure

Image
In this article I want to show you how to use the Azure Account Storage and a CDN associate to the Storage account already mentioned. Explaining the two concepts: Azure Storage Accounts Is a component on Azure platform used to storage files, data and anyother information we want to. The storage account can be: Blob Storage: for store files like we use on our PC. Files Storage : for File sharing using the SMB protocol, with this we can for example read and write the same file by multiple VMs.. Table Storage : for store data like noSql, is used to store data like database. Queues Storage : for store and retrieve messages, to scale apps depending on traffic. In this article we are going to focus on Blob Storage. Azure CDN CDN stands for Content Delivery Network and is a secure, reliable content delivery that allow our app access the static content faster lighten up the load of the server and enriching the client experience. What you need to make it ...
Read more