JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 91

Question

Explain how to implement a simple dependency injection container.

Answer

Why Dependency Injection?

  • Loose Coupling: DI promotes loose coupling between components. Instead of classes directly creating their dependencies, they receive them as parameters. This makes code more modular, testable, and easier to maintain.

  • Reusability: Dependencies can be swapped out easily without modifying the core logic of a class, allowing for flexibility and reuse across different parts of your application.

Basic JavaScript DI Container

class DependencyInjectionContainer {
  constructor() {
    this.dependencies = {}; 
  }

  register(name, dependency) {
    this.dependencies[name] = dependency;
  }

  resolve(name) {
    return this.dependencies[name];
  }
}

// Example Usage

class Database {
  constructor() {
    console.log("Database connected"); 
  }
}

class UserService {
  constructor(database) {
    this.database = database;
  }

  getUserById(id) {
    console.log(`Fetching user with ID ${id} using database:`, this.database);
  }
}

const container = new DependencyInjectionContainer();
container.register('Database', Database); // Register the Database dependency

const userService = container.resolve('UserService'); 
userService.getUserById(1);

Explanation:

  1. DependencyInjectionContainer Class: This class acts as our DI container. It has a dependencies object to store registered dependencies by name.

  2. register(name, dependency) Method: Used to add dependencies to the container. The name is used to identify the dependency later, and dependency is the actual instance or constructor function of the class.

  3. resolve(name) Method: Retrieves a registered dependency by its name. It returns the associated instance or function.

  4. Example Usage:

    • We define a Database class to represent database interactions (simplified).

    • The UserService class depends on a database. Instead of creating the database directly, it takes it as a parameter in its constructor.

    • In the main part:

      • We create an instance of DependencyInjectionContainer.

      • We register the Database class with the container using container.register('Database', Database).

      • We resolve the UserService (which depends on the Database), and it receives a database instance injected by the container.

Key Points:

  • Flexibility: You can easily change dependencies without modifying classes that use them.

  • Testability: It's much easier to test individual components when they receive their dependencies through injection, allowing you to control what they interact with during tests.

PreviousQuestion 90NextQuestion 92

Last updated 9 months ago