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

Post a Comment

Popular posts

Python [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier

  Error requests.exceptions.SSLError: HTTPSConnectionPool  Max retries exceeded with url:  (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)'))). Analysis & Solution Recently, we updated from Python 3.11 to 3.13, which resulted in error above. We did verify AKI = SKI in chain of certificates. Also, imported chain of certificates into certifi. Nothing worked for us. Seemingly, it is a bug with Python 3.13. So, we downgraded to Python 3.12 and it started working. Other problems and solution -  '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)'))) solution  pip install pip-system-certs [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired  (_ssl.c:1006) solution  1# openssl s_client -showcerts -connect  signin.aws.amazon.com:443  </dev/...
Post a Comment
Read more




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...
Post a Comment
Read more




MongoDB Regex Query taking more time in Production but same query perform well in UAT

   We came across a situation where-in, MongoDB Query was taking more time in Production like 10 seconds and 4.2 seconds but same query performed well in UAT taking under 400 ms. The very first thought that was evident to us that it is because of amount of data which differed in UAT and Production. Then we ran following to see the execution plan -   db.collection.aggregate(<queries>).explain() This gave us Winning and Rejected Plans. Under which, we analyzed that although it was using 'IXSCAN.' But, it was incorrect index- as we had one compound index built on time field and other fields, and there was other index just on time field for TTL purposes. Winning plan picked TTL index rather than compound index. Thus, we dropped TTL index and built TTL index on a different time field.  That got our query performance time from 10 seconds to 726 ms. Also, for other query the performance came down from 8 seconds to 4.3 seconds. Then, we ran following -  ...
Post a Comment
Read more




What is Leadership

 
Post a Comment
Read more




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...
Post a Comment
Read more