Java Factory Pattern Explained

Last Updated:
By: Lokesh Gupta
Creational Patterns
Design Patterns

What is the most usual method of creating an instance of a class in java? Most people will answer this question: “using new keyword“. Well, it is considered old-fashioned now. Let’s see how??

If object creation code is spread in the whole application, and if you need to change the process of object creation then you need to go in each and every place to make necessary changes. After finishing this article, while writing your application, consider using the Java factory pattern.

In my previous post, “Singleton design pattern in java“, we discussed various ways to create an instance of a class such that there can not exist another instance of same class in same JVM.

In this post, I will demonstrate another creational pattern, i.e. Factory pattern, for creating instances for your classes. Factory, as the name suggests, is a place to create some different products which are somehow similar in features yet divided into categories.

In Java, factory pattern is used to create instances of different classes of the same type.

Table of Contents

1. When to implement factory pattern?
2. Factory Pattern Implementation
3. Advantages of factory pattern
4. Final notes

1. When to use factory pattern?

Factory pattern introduces loose coupling between classes which is the most important principle one should consider and apply while designing the application architecture. Loose coupling can be introduced in application architecture by programming against abstract entities rather than concrete implementations. This not only makes our architecture more flexible but also less fragile.

A picture is worth a thousand words. Let’s see how a factory implementation will look like.

class_diagram_of_factory_pattern_in_java1-8964987

Above class-diagram depicts a common scenario using an example of a car factory which is able to build 3 types of cars i.e. small, sedan and luxury. Building a car requires many steps from allocating accessories to final makeup. These steps can be written in programming as methods and should be called while creating an instance of a specific car type.

If we are unfortunate then we will create instances of car types (e.g. SmallCar) in our application classes and thus we will expose the car building logic to the outside world and this is certainly not good. It also prevents us in making changes to car making process because the code is not centralized, and making changes in all composing classes seems not feasible.

2. Java Factory Pattern Example

So far we have design the classes need to be designed for making a CarFactory. Let’s create them now.

2.1. Object types

CarType will hold the types of car and will provide car types to all other classes.

package designPatterns.creational.factory;

public enum CarType {
    SMALL, SEDAN, LUXURY
}

2.2. Object implementations

Car is parent class of all car instances and it will also contain the common logic applicable in car making of all types.

package designPatterns.creational.factory;

public abstract class Car {

	public Car(CarType model) {
		this.model = model;
		arrangeParts();
	}

	private void arrangeParts() {
		// Do one time processing here
	}

	// Do subclass level processing in this method
	protected abstract void construct();

	private CarType model = null;

	public CarType getModel() {
		return model;
	}

	public void setModel(CarType model) {
		this.model = model;
	}
}

LuxuryCar is concrete implementation of car type LUXURY.

package designPatterns.creational.factory;

public class LuxuryCar extends Car {

	LuxuryCar() {
		super(CarType.LUXURY);
		construct();
	}

	@Override
	protected void construct() {
		System.out.println("Building luxury car");
		// add accessories
	}
}

SmallCar is concrete implementation of car type SMALL.

package designPatterns.creational.factory;

public class SmallCar extends Car {

	SmallCar() {
		super(CarType.SMALL);
		construct();
	}

	@Override
	protected void construct() {
		System.out.println("Building small car");
		// add accessories
	}
}

SedanCar is concrete implementation of car type SEDAN.

package designPatterns.creational.factory;

public class SedanCar extends Car {

	SedanCar() {
		super(CarType.SEDAN);
		construct();
	}

	@Override
	protected void construct() {
		System.out.println("Building sedan car");
		// add accessories
	}
}

2.3. Factory to create objects

CarFactory.java is our main class implemented using factory pattern. It instantiates a car instance only after determining its type.

package designPatterns.creational.factory;

public class CarFactory {
	public static Car buildCar(CarType model) {
		Car car = null;
		switch (model) {
		case SMALL:
			car = new SmallCar();
			break;

		case SEDAN:
			car = new SedanCar();
			break;

		case LUXURY:
			car = new LuxuryCar();
			break;

		default:
			// throw some exception
			break;
		}
		return car;
	}
}

2.4. Test factory pattern

In TestFactoryPattern, we will test our factory code. Lets run this class.

package designPatterns.creational.factory;

public class TestFactoryPattern {
	public static void main(String[] args) {
		System.out.println(CarFactory.buildCar(CarType.SMALL));
		System.out.println(CarFactory.buildCar(CarType.SEDAN));
		System.out.println(CarFactory.buildCar(CarType.LUXURY));
	}
}

Program Output.

Building small car
designPatterns.creational.factory.SmallCar@7c230be4
Building sedan car
designPatterns.creational.factory.SedanCar@60e1e567
Building luxury car
designPatterns.creational.factory.LuxuryCar@e9bfee2

As you can see, the factory is able to return any type of car instance it is requested for. It will help us in making any kind of changes in car making process without even touching the composing classes i.e. classes using CarFactory.

3. Benefits of factory pattern

By now, you should be able to count the main advantages of using the factory pattern. Let’s note down:

  1. The creation of an object precludes its reuse without significant duplication of code.
  2. The creation of an object requires access to information or resources that should not be contained within the composing class.
  3. The lifetime management of the generated objects must be centralized to ensure a consistent behavior within the application.

4. Final notes

Factory pattern is most suitable where there is some complex object creation steps are involved. To ensure that these steps are centralized and not exposed to composing classes, factory pattern should be used. We can see many realtime examples of factory pattern in JDK itself e.g.

I hope, I have included enough information in this Java factory pattern example to make this post informative.

If you still have some doubt on abstract factory design pattern in Java, please leave a comment. I will be happy to discuss with you.

Happy Learning !!

Was this post helpful?

Recommended Reading:

  1. Abstract Factory Pattern Explained
  2. Java Singleton Pattern Explained
  3. Immutable Collections with Factory Methods in Java 9
  4. TestNG @Factory
  5. TestNG – @Factory vs @DataProvider
  6. Spring static factory-method example
  7. Prototype design pattern in Java
  8. Builder Design Pattern
  9. Decorator Design Pattern in Java
  10. Adapter Design Pattern in Java

Join 7000+ Awesome Developers

Get the latest updates from industry, awesome resources, blog updates and much more.

* We do not spam !!

51 thoughts on “Java Factory Pattern Explained”

  1. in factory pattern.
    If we have 1 laks sub classes ,then how to create factory.

    if else condition,we cant put in factory class for 1 laks subclassess.
    Please explain.

    Reply

    • We can use Reflection but it is costly and usecase specified by you doesn’t make sense either.
      Anyway below is the partial code snipet.

      1. Modify CarType enum to include classname as well.
      Like for SMALL –> SmallCar etc.

       
public enum CarType{
    SMALL("SmallCar");
    private String className;
    public String getClassName(){return className;}
    public void setClassName(String className){this.className = className;}
    private CarType(String className){this.className = className;}
}
2. You can iterate over CarType enum.

public static Car buildCar(CarType model) {
        Car car = null;
       for(CarType carType : CarType.values) {
           if(model.equals(carType)) {
               car = Class.forName(carType.getClassName()).getConstructor().newInstance();
               break;
           }
       }
    if(null == car){
         // throw some exception
   } 
  return car;
}
      Reply

  2. What if we need to add another car type as SUV then we need to change CarFactory which is not good practice as it voilates Open close principle.am i correct?

    Reply

    • Adding a new CarType should not violate Open Close principle as we are not modifying any functionality of factory class by adding logic to create instance for SUV.
      It works as it was working earlier.

      Reply

      • Hi Shivan, Yes you are correct, but CarFactory class changes if we add new car type, So CarFactory class violate OCP,
        Instead of if else or for loop, We can create separate factory for each car type and let client decide to choose.
        Please share your though on this. Thanks

        Reply

    • “Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.”

      In case of you adding another if -else/ switch case, you are sort of extending the functionality of providing with another type of object but somewhat of the same type (thanks to abstract class/interface).But you are not modifying it.

      I build a factory today to produce different kinds of chips, package and sell them. I start with potato chips and then EXTEND to produce banana chips. I am extending my functionality, not modifying the behaviour, I AM STILL A CHIPS FACTORY.

      In case you have a library which today provides you with 3 Types of objects, – CAR, if you want to modify it and also provide with a ELECTRIC CAR, you have to recompile and provide the new upgraded jars. But you are still providing cars.

      If you completely change/modify the behaviour it will be a problem. I think this is what OCP means. PLease pitch in in case it is wrong. Thanks

      Reply

  4. Definitely, if it’s “modern” or “up-to-date” to instantiate classes in Java within a switch case statement, you need to change your programming language right now. Consider moving your skills to a professional programming language. You are working very hard in Java. A real software development don’t need to be very hard. Regards.

    Reply

    • Hi Fabian, Thanks for the suggestion but perhaps it will be unnecessary. I really looked up in outer world to find if I am THE alien, but found plenty of guys like this.

      I will not say that you are incorrect, but will appreciate if you can express your thoughts with facts/reasons. OR you can suggest your edit in wikipedia page because there I could see the same thing.

      Reply

  5. Hi Lokesh,
    How do you avoid casting after getting back an instance?

    LuxuryCar lc= (LuxyryCar) FactoryManager.buildCar(CarType.LUXURY);

    Reply

  8. I might sound silly , why the concrete classes (Sedan,etc) are public. Since we are exposing a factory class to create us instance , it doesn’t make sense to have them public right , any one can create new instance of these classes directly from anywhere, ain’t they ??

    Reply

  9. Hi in the original GOF factory pattern, there is a concept of having a creator and a concrete creator. I find this missing in your example. The CarFactory class is of course the concrete creator , but it does not extend from an abstract class / interface (creator)

    So is it OK to call it a factory pattern without having the creator / concrete creator

    Reply

  10. It’s impossible to read this article on Samsung Galaxy 10.1 – the black advert strip jumps to the center of the webpage and covers the article text.

    Reply

  11. How to reuse the same object? i.e If we call – CarFactory.buildCar(CarType.SMALL) multiple times, it returns a new object for every call.

    Regards,
    Praveen Das

    Reply

    • Hi Praveen, another question in response to your question. Why would a factory will return the same instance on each request? What’s use of this approach? I believe you will have a good reason for it, so please share with us. It will expand our thought process as well.

      To answer your question, you can apply singleton pattern on different Car objects and return from construct() method.

      On another thought, you should better using prototype pattern, if you want to save some CPU cycles in car construction process. Singleton simply doesn’t make sense to me.

      https://howtodoinjava.com/design-patterns/creational/prototype-design-pattern-in-java/

      Reply

      • Hi Lokesh, I’m looking at implementing a mailbox which fetches messages at a specific time interval.

        Each messages fall under different types of validations, so depending on the NotificationType i call the ValidationFactory.

        since there are for ex:22 notifications, and 100 messages, the notifications can be of same type. in this case i should be able to reuse the already created object for that particular NotificationType.

        NotificationType would be my enum class.

        ValidationService would be the parent class for all validation instances.

        ValidationFactory would get me the respective object for the notificationType as input.

        Regards,
        Praveen

        Reply

        • I don’t think that Factory is the pattern you are looking for. However if you really want to use Factory pattern as your approach you should combine it with a caching adapter for the actual Factory which returns the cached instances.

          Reply

  12. Thanks for this wonderful example. My doubt is why do I get a warning in my IDE that the method “construct()” shouldn’t be called in side the construtor because it’s an overridable method?

    I read that it has something to do with inheritance and if other classes extend this class things COULD go wrong down the line if someone overrides that method in another place.

    Did I understand correctly the potencial danger here?

    Reply

    • There is a danger in doing this and you should not do it (add overridable methods in the constructor)

      Effective Java 2nd Edition, Item 17: Design and document for inheritance or else prohibit it

      “There are a few more restrictions that a class must obey to allow inheritance. Constructors must not invoke overridable methods, directly or indirectly. If you violate this rule, program failure will result. The superclass constructor runs before the subclass constructor, so the overriding method in the subclass will get invoked before the subclass constructor has run. If the overriding method depends on any initialization performed by the subclass constructor, the method will not behave as expected.”

      Reply

  15. I guess there is one small mistake (inaccuracy) in your example.
    You have to make method constcut() abstract and put it into constructor instead of method arrangeParts():
    public Car(CarType model) {
    this.model = model;
    //arrangeParts(); // remove this. You cold leave it but it just misslead you, it has nothing to design pattern.
    construct(); // abstrac method! will be called implementation from interited class.
    }
    Then constructor LuxuryCar will look like:
    LuxuryCar() {
    super(CarType.LUXURY);
    //construct(); // remove this!
    }

    Reply

  16. Good post, thank you. Could you make it a bit more complex (as part2) in the way, lets say: Car is composed of underframe, engine and body and each of this component is created by factory depending of type of a car. What I’d like to see is how those factories will be used together, where to put it, how to call it. Thanks

    Reply

  21. You did not mention where CarFactory.buildCar() should be called… You have just written the testing part but I suppose the integration part is missed…

    Reply

Leave a Comment

HowToDoInJava

A blog about Java and related technologies, the best practices, algorithms, and interview questions.

Meta Links

About Me

Contact Us

Privacy policy

Advertise

Guest Posts

Blogs

REST API Tutorial