Skip to main content

Java Design Patterns: Simple Factory pattern

Design Patterns are much talked about yet much feared of, much explained and yet much confused topic. A lot of fundamentals used in Design Patterns are actually application of basic Object Oriented Design principles.

Take example of 'Simple Factory' (or just 'Factory') pattern, which is not actually a pattern but more of a good design practice. Think of a scenario where you need to create a different variant of some class depending on some condition.

E.g. You have a base class House and various sub classes extending House, say Villa, Flat and Penthouse.

Now depending on some user input, say price range, you need to use objects of Villa, Flat or Penthouse to perform some function.


public double getHouseArea(double higherPriceRange){
    House house;

    if(higherPriceRange < 4000000){
      house = new Flat();
    }else if(higherPriceRange < 10000000){
      house = new Villa();
    }else{
      house = new Penthouse();
    }
    
    return house.getArea();
}

Now assume there is another similar function and you need to write the House creation code (code in blue) again! And what if we decide to add another type of house to our system, say a Treehouse, we will have to go an alter code in ALL those methods.

Won't it be a better idea to move all this code to a separate place and call that code in all the methods, so that in case of any kind of change, we have to update code in just one place.

How about this:

public class HouseFactory{
   
  public static createHouse(double higherPriceRange){
    House house;
    if(higherPriceRange < 4000000){
      house = new Flat();
    }else if(higherPriceRange < 10000000){
      house = new Villa();
    }else{
      house = new Penthouse();
    }
    return house;
  }
  
}


public double getHouseArea(double higherPriceRange){
    House house = HouseFactory.createHouse(higherPriceRange);       
    return house.getArea();
}

Awesome right? Yeah. Elementary? Absolutely.

If you noticed we just followed the basic principle of 'encapsulate what varies'. Since the House creation code can vary if any new types of houses are added, we just rounded it off to a separate class. Also this avoids code duplication across various classes.

As I said, this is not a design pattern. It is just a simple design idiom. But whatever it is, no reason for us to not use it!


Comments

Popular posts from this blog

How I converted a table in an email to a graph on a website? Hint: Azure Functions and Logic App

This mini-project started as a necessity.  I get an email like this everyday, which gives daily numbers for different metrics. The problem with such an email is that it is difficult to keep track of or gauge the rate of growth of these metrics. If you want to know how what the previous day's numbers were you need to go to the previous day's email.  The better option any day is to have a graph that shows the values of the metrics every day. Something like this: With this goal I set out to make this system but with as less coding and expenses as possible.  First obvious step in the process was to get hold of the email and extract its text. The easiest way to do this is to use Azure Logic App.  Here is what my logic app looks like: When any new email arrives in my Outlook 365 account, with a subject that contains "System usage Stats as on", it passes the body of the email to an Azure function named 'EmailTextCleanerFunction' (code below), whose job is to clean an...

Changing Eclipse Workspace Directory

Recently I moved my entire Eclipse installation directory but the workspace was still getting created in the older location only. And worst there was no option to select the Workspace directory in the Window->Options->Workspace menu. To change the workspace location in Eclipse do this. Goto ECLIPSE_HOME\configuration\.settings directory, edit the org.eclipse.ui.ide.prefs file and change the RECENT_WORKSPACES value to the desired location. If you want that Eclipse prompts you to select workspace when you start it, change the SHOW_WORKSPACE_SELECTION_DIALOG value to true. And you are done!

Hands on review: Yahoo! Mail app for Windows 8

Before you start mocking me for using Yahoo! Mail, let me explain that this is NOT my primary mail account and I use Gmail and Outlook.com for my daily use. Yes, this Yahoo! account was once my daily haunt but that was during college days and those days are long gone. I don't use Yahoo! Mail much but still there are some group subscriptions and I just log in once in a while to see what's happening in those forgotten groups. And due to this reason, I have always kept track of changes in Yahoo! Mail and the fact is that you can blame them for everything but not really lack of trying. Though most of those tries just ended up cluttering the UI and adding somewhat needless features. However, now we hear that new CEO Marissa Mayer is focusing once again on the mail and first major product to come out is Yahoo! Mail app for Windows 8. So how is it? The Login screen is pretty neat and purple background with an envelope watermark is very pleasing, very Yahoo!. However why ...