Skip to main content

Design Patterns (aka DP), Creational - Abstract Factory Pattern

DP is a well-described solution to a common software problem. Its benefits:

  • Already defined to solve a problem.
  • Increase code reusability and robustness.
  • Faster devlopment and new developers in team can understand it easily
DP defined in to 3 categories:
  • Creational - Used to construct objects such that they can be decoupled from their implementing system.
  • Structural - Used to form large object structures between many disparate objects
  • Behavioral - Used to manage algorithms, relationships, and responsibilities between objects.
To understand this please read factory pattern.

When you go through factory pattern:
  • You see that factory can produce only Computers or aptly varied types of Computers. But only Computers.
  • Now, Say you have a 3rd variety of Computer just like PC or Server. Say, Laptop class. You can easily inherit Computer an create your Laptops.
  • So, once you have Laptop. Thus your factory start delivering it automatically? No, that would require a bit modification to have place for Laptops.
  • That means, Laptop's are not automatically plugged-in to existing factory. Existing factory requires modifications to do so.
  • Now, If you modify existing Factory it would require testing, if it is working correctly.
  • Now, say earlier both PC and Server were manufactured by same Factory. But now PC is produced by different Factory and Server is produced by different.
  • What then!! Do client need to go to different factories for purchasing Computers?
If you get above bullets. Now as a consumer, I do not want to go to different factories neither as a producer, I want to modify my existing Factory.

Scenario:-
  • You have an interface or abstract class or normal class. Computer class.
  • For now you have only 1 implementation of Computer. That is, PC class.
  • Now, you need Factory for PC. But as you have seen above problems, you want your Factory to be designed in such a way that it does not require modification for a new Computer.
  • So, you create an abstract interface. ComputerAbstractFactory class.
  • Now you create a PC Factory inheriting ComputerAbstractFactory class.
  • Now, as a client I do not want to go to PC Factory. I want to go to only single Factory that produces Computers.
  • So, we create a class ComputerFactory that provides you Computers of any types provided client needs to tell them specific factories for item they need.
Uptil now Client is happy as it does not need to go to various factories. It just need to ask ComputerFactory to get him what he needs.
Producer is also happy as now he knows PC factory will only produce PC nothing else.
  • There is another kind of Computer in market. That is Server class.
  • And there is another company that created Server Factory to manufacture Servers.
With Abstract factory we do not need to worry to modify any of existing Factories. Client will just ask ComputerFactory to get him Servers from Server Factory.

package com.test.command.dp.creational.abstarctFactory;

public abstract class Computer {

       public abstract String getRAM();

       public abstract String getHDD();

       public abstract String getCPU();

       @Override
       public String toString() {

              return "RAM= " + this.getRAM() + ", HDD=" + this.getHDD() + ", CPU="
                           + this.getCPU();
       }

}

package com.test.command.dp.creational.abstarctFactory;

public class PC extends Computer {

       private String ram;
       private String hdd;
       private String cpu;

       public PC(String ram, String hdd, String cpu) {
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public String getRAM() {
              // TODO Auto-generated method stub
              return this.ram;
       }

       @Override
       public String getHDD() {
              // TODO Auto-generated method stub
              return this.hdd;
       }

       @Override
       public String getCPU() {
              // TODO Auto-generated method stub
              return this.cpu;
       }

}

package com.test.command.dp.creational.abstarctFactory;

public interface ComputerAbstractFactory {

       public Computer createComputer();
}

package com.test.command.dp.creational.abstarctFactory;

public class PCFactory implements ComputerAbstractFactory {

       private String ram;
       private String hdd;
       private String cpu;

       public PCFactory(String ram, String hdd, String cpu) {
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public Computer createComputer() {
              // TODO Auto-generated method stub
              return new PC(ram,hdd,cpu);
       }

}

package com.test.command.dp.creational.abstarctFactory;

public class ComputerFactory {

       public static Computer getComputer(ComputerAbstractFactory factory){
              return factory.createComputer();
       }
}

package com.test.command.dp.creational.abstarctFactory;

public class Server extends Computer {

       private String ram;
       private String hdd;
       private String cpu;
      
      

       public Server(String ram, String hdd, String cpu) {
             
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public String getRAM() {
              // TODO Auto-generated method stub
              return this.ram;
       }

       @Override
       public String getHDD() {
              // TODO Auto-generated method stub
              return this.hdd;
       }

       @Override
       public String getCPU() {
              // TODO Auto-generated method stub
              return this.cpu;
       }

}



package com.test.command.dp.creational.abstarctFactory;

public class ServerFactory implements ComputerAbstractFactory {

       private String ram;
       private String hdd;
       private String cpu;

       public ServerFactory(String ram, String hdd, String cpu) {
              this.ram = ram;
              this.hdd = hdd;
              this.cpu = cpu;
       }

       @Override
       public Computer createComputer() {
             
              return new Server(ram,hdd,cpu);
       }
      
      
}

package com.test.command.dp.creational.abstarctFactory;

public class TestDesignPatterns {

       /**
        * @param args
        */
       public static void main(String[] args) {
              testAbstractFactory();

       }

       private static void testAbstractFactory() {
              Computer pc = ComputerFactory.getComputer(new PCFactory(null, null, null));
              Computer server = ComputerFactory.getComputer(new ServerFactory(null, null, "2"));
             
              System.out.println("Dinesh Sachdev your PC is ready:"+pc);
              System.out.println("Dinesh Sachdev your Server is ready server);    
             
       }

}


Comments

Popular posts

Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Scala Spark building Jar leads java.lang.StackOverflowError

  Exception -  [Thread-3] ERROR scala_maven.ScalaCompileMojo - error: java.lang.StackOverflowError [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.TraversableForwarder$class.isEmpty(TraversableForwarder.scala:36) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.isEmpty(ListBuffer.scala:45) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.toList(ListBuffer.scala:306) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.result(ListBuffer.scala:300) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:31) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:27) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.GenericCompanion.apply(GenericCompanion.scala:50) [Thread-3] INFO scala_maven.ScalaCompile...




MongoDB Chunk size many times bigger than configure chunksize (128 MB)

  Shard Shard_0 at Shard_0/xyz.com:27018 { data: '202.04GiB', docs: 117037098, chunks: 5, 'estimated data per chunk': '40.4GiB', 'estimated docs per chunk': 23407419 } --- Shard Shard_1 at Shard_1/abc.com:27018 { data: '201.86GiB', docs: 116913342, chunks: 4, 'estimated data per chunk': '50.46GiB', 'estimated docs per chunk': 29228335 } Per MongoDB-  Starting in 6.0.3, we balance by data size instead of the number of chunks. So the 128MB is now only the size of data we migrate at-a-time. So large data size per chunk is good now, as long as the data size per shard is even for the collection. refer -  https://www.mongodb.com/community/forums/t/chunk-size-many-times-bigger-than-configure-chunksize-128-mb/212616 https://www.mongodb.com/docs/v6.0/release-notes/6.0/#std-label-release-notes-6.0-balancing-policy-changes




AWS EMR Spark – Much Larger Executors are Created than Requested

  Starting EMR 5.32 and EMR 6.2 you can notice that Spark can launch much larger executors that you request in your job settings. For example - We started a Spark Job with  spark.executor.cores  =   4 But, one can see that the executors with 20 cores (instead of 4 as defined by spark.executor.cores) were launched. The reason for allocating larger executors is that there is a AWS specific Spark option spark.yarn.heterogeneousExecutors.enabled (exists in EMR only, does not exist in Open Source Spark) that is set to true by default that combines multiple executor creation requests on the same node into a larger executor container. So as the result you have fewer executor containers than you expected, each of them has more memory and cores that you specified. If you disable this option (--conf "spark.yarn.heterogeneousExecutors.enabled=false"), EMR will create containers with the specified spark.executor.memory and spark.executor.cores settings and will not co...




Hive Count Query not working

Hive with Tez execution engine -  count(*) not working , returning 0 results.  Solution -  set hive.compute.query.using.stats=false Refer -  https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties hive.compute.query.using.stats Default Value:  false Added In: Hive 0.13.0 with  HIVE-5483 When set to true Hive will answer a few queries like min, max, and count(1) purely using statistics stored in the metastore. For basic statistics collection, set the configuration property  hive.stats.autogather   to true. For more advanced statistics collection, run ANALYZE TABLE queries.