Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Factory Design Pattern

DZone's Guide to

The Factory Design Pattern

Learn all about the factory design pattern, a creational pattern that allows the making of objects with no exposure to instantation logic to the client.

· Java Zone ·
Free Resource

The CMS developers love. Open Source, API-first and Enterprise-grade. Try BloomReach CMS for free.

Factory design pattern is one of the creational patterns. This pattern will allow the creation of objects without exposing the instantiation logic to the client.

Motivation:  During one of the project implementation, we were trying to read the data from multiple sources like a database, CSV and, XML. In this case, we created readers like DatabaseReader, CSVReader and XMLReader etc. But, in the client code we were using the concrete implementations to instantiate the class(For example, XMLReader reader = new XMLReader()) and leading to a lot of duplication of object creational logic across the client code. To overcome this issue, we created an interface called Reader and all the readers implemented the Reader interface. Defined a factory method which will take necessary parameters from the client and creates the required object.

DesignElements: The below design elements are required to use factory design pattern.

  • Product<interface> – defines the interface of objects the factory method creates.
  • ConcreteProduct – implements the product interface
  • Creator – declares the factory method, which returns an object of type Product. The creator may also define a default implementation of the factory method that returns a default ConcreteProduct object.

Implementation:

factory design pattern






Example:

              In this example, we will create Reader objects to read Database, CSV and XML data by using “Factory Design Pattern.” As a first step, we will create Reader interface.


package org.smarttechie;

public interface Reader {
 public String read();
}

Now, we will provide the implementation for Reader interface to read the database.



package org.smarttechie;

public class DataBaseReader implements Reader {

@Override
 public String read() {

 return "Reading database";
 }

}

The implementation to read CSV and XML data.



package org.smarttechie;

public class XMLReader implements Reader {

@Override
 public String read() {

 return "XML file reader";
 }

}


package org.smarttechie;

public class CSVReader implements Reader {

@Override
 public String read() {
 return "CSV file reading";
 }

}

Now, we will create factory method to create reader objects.



package org.smarttechie;

public class ReaderFactory {

public static Reader getReader(String readerType) {
 Reader reader = null;
 if (readerType.equalsIgnoreCase("XML")) {
     reader = new XMLReader();
 } else if (readerType.equalsIgnoreCase("CSV")) {
     reader = new CSVReader();
 } else if (readerType.equalsIgnoreCase("DB")) {
     reader = new DataBaseReader();
 }
 return reader;
 }
}

With a test class, we will test the factory design pattern.


package org.smarttechie;
public class FactoryPatternTest {

/**
 * @param args
 */
 public static void main(String[] args) {
 System.out.println(ReaderFactory.getReader("XML").read());
 }
}

In the above code, we need to ask the ReaderFactory to get the specific reader. So, client code doesn't need to know  the implementation of the concrete reader classes. The code used in this article is available here.

BloomReach CMS: the API-first CMS of the future. Open-source & enterprise-grade. - As a Java developer, you will feel at home using Maven builds and your favorite IDE (e.g. Eclipse or IntelliJ) and continuous integration server (e.g. Jenkins). Manage your Java objects using Spring Framework, write your templates in JSP or Freemarker. Try for free.

Topics:
creational patterns ,factory pattern ,factory design ,java

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}