Dependency injection in controllers in Laravel - Performance & Optimization

Performance: Dependency injection in controllers

MEDIUM IMPACT

This affects the server-side response time and memory usage, indirectly influencing page load speed by optimizing controller instantiation and reducing unnecessary object creation.

Injecting services into controllers for handling requests

Laravel

<?php
class UserController extends Controller {
    protected UserService $service;
    public function __construct(UserService $service) {
        $this->service = $service;
    }
    public function index() {
        return $this->service->getAllUsers();
    }
}

Injecting the service once via constructor avoids repeated instantiation, reducing CPU and memory overhead.

📈 Performance Gainreduces server CPU usage and memory allocation per request, improving response time

Injecting services into controllers for handling requests

Laravel

<?php
class UserController extends Controller {
    public function index() {
        $service = new UserService();
        return $service->getAllUsers();
    }
}

Creating a new service instance inside each method causes repeated object creation and increases memory usage per request.

📉 Performance Costadds unnecessary CPU and memory usage per request, increasing server response time

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
New service instance inside method	N/A (server-side)	N/A	N/A	[X] Bad
Constructor dependency injection	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Dependency injection in controllers happens on the server before the response is sent. Efficient injection reduces server processing time but does not directly affect browser rendering stages.

→Server Request Handling

→Controller Instantiation

⚠️ BottleneckRepeated object creation in controller methods increases server CPU and memory usage.

Optimization Tips

1Inject dependencies once in the controller constructor to avoid repeated object creation.

2Avoid creating service instances inside controller methods to reduce CPU and memory overhead.

3Efficient dependency injection improves server response time but does not directly impact browser rendering.

Performance Quiz - 3 Questions

What is the main performance benefit of using dependency injection in Laravel controllers?

A Improves browser paint speed

B Decreases DOM node count

C Reduces repeated object creation and lowers server CPU usage

D Reduces CSS selector complexity

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the server response time for controller actions.

What to look for: Look for faster server response times indicating efficient controller processing.

Practice

1. What is the main purpose of dependency injection in Laravel controllers?

easy

A. To automatically provide required objects to the controller

B. To manually create objects inside controller methods

C. To make controllers dependent on global variables

D. To avoid using any external classes in controllers

Solution

1. Step 1: Understand dependency injection concept

   Dependency injection means Laravel automatically gives the controller the objects it needs without manual creation.

2. Step 2: Identify the purpose in Laravel controllers

   This keeps controllers clean and easy to test by providing dependencies automatically.

3. Final Answer:

   To automatically provide required objects to the controller -> Option A

4. Quick Check:

   Dependency injection = automatic object provision [OK]

Hint: Dependency injection means Laravel gives needed objects automatically [OK]

Common Mistakes:

• Thinking you must create objects manually inside controllers
• Confusing dependency injection with global variables
• Believing dependency injection removes use of external classes

2. Which of the following is the correct way to inject a service into a Laravel controller constructor?

easy

A. public function __construct($service) { $this->service = new Service(); }

B. public function __construct(Service $service) { $this->service = $service; }

C. public function __construct() { $this->service = Service::class; }

D. public function __construct(Service $service) { $service = new Service(); }

Solution

1. Step 1: Check constructor parameter type hinting

   public function __construct(Service $service) { $this->service = $service; } correctly type hints the Service class in the constructor parameter.

2. Step 2: Verify assignment to class property

   public function __construct(Service $service) { $this->service = $service; } assigns the injected service to a class property for later use, which is correct.

3. Final Answer:

   public function __construct(Service $service) { $this->service = $service; } -> Option B

4. Quick Check:

   Constructor injection = type hint + assign property [OK]

Hint: Type hint service in constructor and assign to property [OK]

Common Mistakes:

• Not type hinting the service class in constructor
• Creating new service instance inside constructor instead of injecting
• Assigning class name string instead of object

3. Given this controller method, what will be the output if the injected service returns 'Hello' from its greet() method?

public function show(Service $service) {
    return $service->greet();
}

medium

A. "Hello"

B. Error: Service not found

C. null

D. "greet"

Solution

1. Step 1: Understand method injection

   The Service object is injected automatically into the show method by Laravel.

2. Step 2: Call the greet() method on the injected service

   The greet() method returns the string "Hello", so the method returns "Hello".

3. Final Answer:

   "Hello" -> Option A

4. Quick Check:

   Injected service method output = "Hello" [OK]

Hint: Injected method returns service method result directly [OK]

Common Mistakes:

• Assuming service is not injected and causes error
• Expecting method name instead of method return value
• Confusing null with empty string output

4. What is wrong with this controller constructor for dependency injection?

public function __construct(Service $service) {
    $service = new Service();
    $this->service = $service;
}

medium

A. It lacks type hinting for the service parameter

B. It does not assign the service to a class property

C. It creates a new Service instance instead of using the injected one

D. It should not use $this keyword inside constructor

Solution

1. Step 1: Analyze the constructor parameter and assignment

   The constructor receives a Service object but immediately overwrites it by creating a new instance.

2. Step 2: Understand why this is wrong

   This defeats dependency injection because the injected object is ignored and a new one is created manually.

3. Final Answer:

   It creates a new Service instance instead of using the injected one -> Option C

4. Quick Check:

   Overwriting injected service = wrong [OK]

Hint: Do not create new instance; use injected object directly [OK]

Common Mistakes:

• Overwriting injected parameter with new instance
• Forgetting to assign injected object to property
• Confusing type hinting with variable assignment

5. You want to inject two services, Logger and Mailer, into a Laravel controller and use them in a method. Which constructor and method setup is correct?

hard

A. public function __construct() { $this->logger = new Logger(); $this->mailer = new Mailer(); } public function notify() { $this->logger->log('Notify'); $this->mailer->send(); }

B. public function __construct(Mailer $mailer) { $this->mailer = $mailer; } public function notify(Logger $logger) { $logger->log('Notify'); }

C. public function __construct(Logger $logger) { $this->logger = $logger; } public function notify(Mailer $mailer) { $mailer->send(); }

D. public function __construct(Logger $logger, Mailer $mailer) { $this->logger = $logger; $this->mailer = $mailer; } public function notify() { $this->logger->log('Notify'); $this->mailer->send(); }

Solution

1. Step 1: Check constructor injection of both services

   public function __construct(Logger $logger, Mailer $mailer) { $this->logger = $logger; $this->mailer = $mailer; } public function notify() { $this->logger->log('Notify'); $this->mailer->send(); } correctly injects both Logger and Mailer in the constructor and assigns them to properties.

2. Step 2: Verify method usage of injected services

   The notify method uses the injected properties to call log and send methods, which is correct.

3. Final Answer:

   public function __construct(Logger $logger, Mailer $mailer) { $this->logger = $logger; $this->mailer = $mailer; } public function notify() { $this->logger->log('Notify'); $this->mailer->send(); } -> Option D

4. Quick Check:

   Inject all services in constructor, use properties in methods [OK]

Hint: Inject all services in constructor, use $this->property in methods [OK]

Common Mistakes:

• Injecting services only in methods instead of constructor
• Creating new instances inside constructor instead of injecting
• Mixing constructor and method injection inconsistently