API resource controllers in Laravel - Performance & Optimization

Performance: API resource controllers

MEDIUM IMPACT

This affects server response time and client rendering speed by organizing API endpoints efficiently.

Handling CRUD operations for an API resource

Laravel

<?php
use App\Http\Controllers\UserController;

Route::apiResource('users', UserController::class);

class UserController extends Controller {
  public function index() { /* list users */ }
  public function store() { /* create user */ }
  public function show($id) { /* show user */ }
  public function update($id) { /* update user */ }
  public function destroy($id) { /* delete user */ }
}

Centralizes CRUD logic in one controller with standardized routes, enabling better caching and faster response generation.

📈 Performance GainReduces server processing time and improves API response consistency, enhancing interaction responsiveness.

Handling CRUD operations for an API resource

Laravel

<?php
// Separate methods scattered in different controllers
class UserController {
  public function createUser() { /* code */ }
  public function updateUser() { /* code */ }
  public function deleteUser() { /* code */ }
  public function getUser() { /* code */ }
}
// Routes defined individually for each method

Scattered methods cause duplicated logic and inconsistent responses, increasing server processing time and maintenance overhead.

📉 Performance CostIncreases server response time due to redundant code and inconsistent caching opportunities.

Performance Comparison

Pattern	Server Processing	Network Payload	Client Rendering	Verdict
Scattered CRUD methods	High due to duplicated logic	Larger due to inconsistent responses	Normal	[X] Bad
API resource controller	Optimized with unified logic	Smaller and consistent JSON payloads	Normal	[OK] Good

Rendering Pipeline

API resource controllers streamline backend logic, reducing server processing before sending JSON responses, which the browser then renders.

→Server Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckServer Processing due to inefficient or duplicated controller logic

Core Web Vital Affected

INP

This affects server response time and client rendering speed by organizing API endpoints efficiently.

Optimization Tips

1Use API resource controllers to unify CRUD operations in one place.

2Leverage Laravel's route caching to speed up route resolution.

3Keep JSON responses consistent and minimal for faster client rendering.

Performance Quiz - 3 Questions

How do API resource controllers improve server response time?

A By increasing the number of routes for each action

B By sending larger JSON payloads

C By centralizing CRUD logic and reducing duplicated code

D By adding more middleware layers

DevTools: Network

How to check: Open DevTools, go to Network tab, filter API calls, and inspect response times and payload sizes for resource endpoints.

What to look for: Look for consistent, small JSON payloads and fast response times indicating efficient API resource controller usage.