Template method design pattern is a behavioural design pattern that is concerned with algorithms and the assignment of responsibilities between objects, as do all patterns that fall in this category.
The speciality of behavioural design patterns is that they not only describe patterns of objects and classes but also the patterns of communication between them. You might have heard of encapsulating object creation, method invocation and other complex interfaces.
What you might not have heard of is encapsulating algorithms. Template method design pattern is all about that. In this article, we will discuss what is Template method design pattern, why it is used, and a simple Template method design pattern java example to demonstrate its use case.
Template method design pattern is a design pattern that provides an abstract definition of an algorithm with the help of an abstract method called Template Method.
Like most of the behavioral design patterns, Template method design pattern uses inheritance to distribute behaviour between classes. In this pattern, each step invokes either an abstract or a primitive operation. A subclass provides additional details to the algorithm by defining the abstract operations.
So, what is the Template method design pattern’s intent? The intent is to define the skeleton of an algorithm by postponing some steps to subclasses i.e. it lets subclasses define certain steps of an algorithm in their own way keeping the structure of the algorithm intact.
Read also: “Singleton Design Pattern — A thoughtful dive into Object Structures and Creation”
Using design patterns such as the Template method design pattern, we can reduce redundancy in code. We will see an example of it soon. Template methods are the basic techniques of code reusability.
If we are to design a framework or a library, there obviously will be common behaviour between classes that have similar structure and purpose and to deal with that we need a design pattern such as this one.
In our case template methods are the means of factoring out common behavior in library classes and frameworks. If you have ever used frameworks like angular, you have certainly come across injecting functions to controllers i.e. use them only when needed or “hook” them in and that will be called by angular itself. Such patterns lead to a principle that says, “Don’t call us we will call you”.
Systems designed with such patterns allow low-level components to hook themselves into the system and the high-level components determine when and how they are needed. This refers to how a parent class calls the operations of a subclass and not the other way around.
Read also: “All you need to know about Template Method Design Pattern”
Let us see an example of the Template method design pattern in java.
#programming #android-app-development #technology #news #design-patterns