Abstract Factory pattern in LLD - Scalability & System Analysis

Scalability Analysis - Abstract Factory pattern

Growth Table: Abstract Factory Pattern

Users / Scale	100 Users	10K Users	1M Users	100M Users
Number of Product Families	Few (2-3)	Moderate (5-10)	Many (20-50)	Very Many (100+)
Factory Instances Created	Low (few factories)	Moderate (multiple factories)	High (many factories)	Very High (complex factory hierarchies)
System Complexity	Simple to moderate	Moderate	High	Very High
Performance Impact	Negligible	Low	Moderate (object creation overhead)	High (factory management overhead)
Memory Usage	Low	Moderate	High	Very High
Maintenance Effort	Low	Moderate	High	Very High

First Bottleneck

The first bottleneck is the factory management and object creation overhead. As the number of product families and factories grows, the system spends more time creating and managing objects through abstract factories. This can slow down response times and increase memory usage, especially if factories create complex or many objects per request.

Scaling Solutions

• Object Pooling: Reuse created objects instead of creating new ones each time to reduce creation overhead.
• Lazy Initialization: Create objects only when needed to save resources.
• Factory Caching: Cache factory instances to avoid repeated instantiation.
• Horizontal Scaling: Distribute factory usage across multiple servers to handle more requests concurrently.
• Modularization: Split factories into modules or microservices to isolate complexity and scale independently.
• Code Generation: Automate factory code creation to reduce maintenance effort at large scale.

Back-of-Envelope Cost Analysis

• Assuming 1000 requests per second per server, each requiring 5 factory-created objects.
• At 10K users, ~10 servers needed to handle 10K requests/sec.
• Memory per object ~1KB, so 5KB per request, 50MB/sec memory churn at 10K users.
• Network bandwidth mostly unaffected by pattern, but horizontal scaling adds inter-service communication overhead.
• Maintenance cost grows with number of factories and product families due to complexity.

Interview Tip

When discussing Abstract Factory scalability, start by explaining what the pattern does: it creates families of related objects without specifying their concrete classes. Then, discuss how as the number of product families grows, object creation overhead and factory management become bottlenecks. Finally, propose concrete solutions like object pooling, caching, and horizontal scaling. Always connect your points to real-world impacts like memory use and response time.

Self Check Question

Your system uses Abstract Factory pattern and your database handles 1000 QPS. Traffic grows 10x. What do you do first?

Answer: First, optimize object creation by implementing object pooling or caching factory instances to reduce overhead. Then, scale horizontally by adding more servers to distribute load. This addresses the factory bottleneck before database scaling.

Key Result

Abstract Factory pattern scales well at small to moderate product families, but object creation overhead and factory management become bottlenecks at large scale. Solutions include object pooling, caching, and horizontal scaling.

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