Abstract Factory pattern in LLD - Architecture Diagram

System Overview - Abstract Factory pattern

The Abstract Factory pattern helps create families of related objects without specifying their exact classes. It provides an interface to create objects, letting the system be flexible and scalable when adding new product types or variants.

This pattern is useful in systems that need to support multiple product families, ensuring that products from one family are used together.

Architecture Diagram

User
  |
  v
Abstract Factory Interface
  |-----------------------------|
  |                             |
Concrete Factory A          Concrete Factory B
  |                             |
  |                             |
Product A1                 Product B1
Product A2                 Product B2

Components

User

client

Requests products from factories without knowing their concrete classes

Abstract Factory Interface

interface

Defines methods to create abstract products

Concrete Factory A

factory

Creates concrete products of family A

Concrete Factory B

factory

Creates concrete products of family B

Product A1

product

A concrete product of family A

Product A2

product

Another concrete product of family A

Product B1

product

A concrete product of family B

Product B2

product

Another concrete product of family B

Request Flow - 5 Hops

User → Abstract Factory Interface

Abstract Factory Interface → Concrete Factory A or B

User → Concrete Factory A or B

Concrete Factory A or B → Product A1/A2 or B1/B2

Concrete Factory A or B → User

Failure Scenario

Component Fails:Concrete Factory

Impact:User cannot create products of that family; system may fail to produce required objects

Mitigation:Use fallback factories or default implementations; validate factory availability before use

Architecture Quiz - 3 Questions

What is the main purpose of the Abstract Factory Interface?

A To manage user requests

B To create concrete product instances directly

C To define methods for creating abstract products

D To store product data

Design Principle

The Abstract Factory pattern separates product creation from usage, allowing the system to be flexible and scalable by supporting multiple product families without changing client code.

Practice

1. What is the main purpose of the Abstract Factory pattern in system design?

easy

A. To create families of related objects without specifying their concrete classes

B. To allow direct instantiation of concrete classes

C. To enforce a single instance of a class

D. To simplify database queries

Solution

1. Step 1: Understand the role of Abstract Factory

   The Abstract Factory pattern is designed to create related objects without exposing their concrete classes.

2. Step 2: Compare options with the pattern's purpose

   To create families of related objects without specifying their concrete classes correctly describes this purpose, while others describe different patterns or unrelated concepts.

3. Final Answer:

   To create families of related objects without specifying their concrete classes -> Option A

4. Quick Check:

   Abstract Factory = Create related objects [OK]

Hint: Abstract Factory creates related objects without concrete classes [OK]

Common Mistakes:

• Confusing Abstract Factory with Singleton pattern
• Thinking it creates only one object
• Mixing it up with Builder or Factory Method

2. Which of the following is the correct way to declare an Abstract Factory interface in a typical object-oriented design?

easy

A. var AbstractFactory = { create: function() { return ProductA; } }

B. class AbstractFactory { new ProductA(); new ProductB(); }

C. function AbstractFactory() { return new ProductA(); }

D. interface AbstractFactory { createProductA(): ProductA; createProductB(): ProductB; }

Solution

1. Step 1: Identify correct interface syntax

   Abstract Factory is usually declared as an interface with methods to create related products.

2. Step 2: Analyze each option

   interface AbstractFactory { createProductA(): ProductA; createProductB(): ProductB; } correctly declares an interface with creation methods. Options A, B, and C do not follow interface or abstract factory conventions.

3. Final Answer:

   interface AbstractFactory { createProductA(): ProductA; createProductB(): ProductB; } -> Option D

4. Quick Check:

   Abstract Factory interface = interface AbstractFactory { createProductA(): ProductA; createProductB(): ProductB; } [OK]

Hint: Abstract Factory uses interface with creation methods [OK]

Common Mistakes:

• Using concrete class instead of interface
• Returning product instances directly in constructor
• Confusing factory function with abstract factory interface

3. Given the following code snippet using Abstract Factory pattern, what will be the output?

class ModernFactory {
  createChair() { return 'Modern Chair'; }
  createSofa() { return 'Modern Sofa'; }
}
class VictorianFactory {
  createChair() { return 'Victorian Chair'; }
  createSofa() { return 'Victorian Sofa'; }
}
function client(factory) {
  console.log(factory.createChair());
  console.log(factory.createSofa());
}
client(new VictorianFactory());

medium

A. Victorian Chair\nVictorian Sofa

B. Modern Chair\nModern Sofa

C. Error: factory methods not found

D. undefined\nundefined

Solution

1. Step 1: Identify which factory is used

   The client function is called with new VictorianFactory(), so VictorianFactory methods will be used.

2. Step 2: Trace method calls and outputs

   VictorianFactory's createChair() returns 'Victorian Chair' and createSofa() returns 'Victorian Sofa'. These are printed.

3. Final Answer:

   Victorian Chair Victorian Sofa -> Option A

4. Quick Check:

   VictorianFactory output = Victorian Chair\nVictorian Sofa [OK]

Hint: Check which factory instance is passed to client [OK]

Common Mistakes:

• Assuming ModernFactory is used instead
• Confusing method names or return values
• Expecting errors due to missing interface

4. In the following Abstract Factory implementation, what is the main issue causing a runtime error?

class Factory {
  createProduct() {
    return new Product();
  }
}
class Product {}
const factory = new Factory();
const product = factory.createProduct();
console.log(product.name.toUpperCase());

medium

A. Missing interface declaration for Factory

B. Product class does not have a 'name' property, causing undefined access

C. Factory class cannot instantiate Product directly

D. createProduct method is not returning an object

Solution

1. Step 1: Analyze the Product class and usage

   The Product class is empty and does not define a 'name' property.

2. Step 2: Understand the console.log statement

   Accessing product.name returns undefined, and calling toUpperCase() on it causes a TypeError runtime error.

3. Final Answer:

   Product class does not have a 'name' property, causing undefined access -> Option B

4. Quick Check:

   Accessing missing property = Product class does not have a 'name' property, causing undefined access [OK]

Hint: Check if accessed properties exist on created objects [OK]

Common Mistakes:

• Thinking Factory cannot instantiate Product
• Expecting interface is mandatory at runtime
• Assuming createProduct returns null or undefined

5. You are designing a UI toolkit that supports multiple themes (Light and Dark). Using the Abstract Factory pattern, which design ensures that all UI components (Button, Checkbox) are consistent with the selected theme?

hard

A. Create Buttons and Checkboxes directly in client code based on theme

B. Use a single factory that creates default Buttons and Checkboxes ignoring theme

C. Create separate factories for Light and Dark themes, each producing themed Buttons and Checkboxes

D. Use a factory that creates only Buttons and let client create Checkboxes

Solution

1. Step 1: Understand the need for consistency

   Abstract Factory helps create families of related objects that match a theme or style.

2. Step 2: Evaluate design options

   Create separate factories for Light and Dark themes, each producing themed Buttons and Checkboxes creates separate factories for each theme, ensuring all components are consistent. Other options break consistency or delegate creation improperly.

3. Final Answer:

   Create separate factories for Light and Dark themes, each producing themed Buttons and Checkboxes -> Option C

4. Quick Check:

   Theme consistency = Separate factories [OK]

Hint: Use one factory per theme to keep components consistent [OK]

Common Mistakes:

• Mixing themes in one factory
• Creating components directly in client code
• Partial factory implementations missing products