Kepiye cara kerja request lifecycle ing Laravel?

Question

IT Interview Practice · Accepted Answer

Saben request Laravel mlebu liwat siji front controller, `public/index.php`, dikendhaleni dening **HTTP Kernel** liwat tumpukan **middleware** lan **router** menyang sawijining **controller**, banjur mbalekake sawijining `Response` — sawise iku middleware **terminable** mlaku.

## Tahap-tahape

```
public/index.php  ── autoload + bootstrap app
   ▼
HTTP Kernel::handle($request)
   ▼
Bootstrappers  ── env, config, providers (register + boot)
   ▼
Global middleware  ── (TrustProxies, HandleCors, ...)
   ▼
Router dispatch  ── cocogake route
   ▼
Route / group middleware  ── (auth, throttle, verified, ...)
   ▼
Controller (utawa closure)  ── logika sampeyan → mbalekake Response
   ▼
Response ──▶ client
   ▼
Kernel::terminate  ── terminable middleware (contone simpen session, logging)
```

1. **Front controller** — `index.php` ngemot Composer autoload lan mbootstrap container aplikasi.
2. **Kernel::handle** — HTTP Kernel nampa `Request` lan nglakokake **bootstrapper**: ngemot env + config, ndaftar lan m**boot** service provider (ing kene framework lan binding sampeyan disambung).
3. **Global middleware** — mlaku kanggo saben request (CORS, mode pangopènan, ngethok string, kapercayan proxy).
4. **Routing** — router nyocokake URI + verb menyang sawijining route.
5. **Route/group middleware** — middleware sing ditugasake menyang route utawa grupe (`auth`, `throttle`, `verified`) mlaku sadurunge controller; saben siji bisa medhot dalan.
6. **Controller** — action (utawa route closure) sampeyan mlaku, nganggo model/service, lan mbalekake sawijining `Response` (view, JSON, redirect). Logika "sawise" duweke middleware mlaku nalika response munggah bali metu.
7. **terminate** — sawise response dikirim, `Kernel::terminate` nglakokake terminable middleware kanggo gawean sing ditundha.

```php
// app/Http/Middleware/Timing.php  → 3/5. middleware
public function handle($request, Closure $next)
{
    $request->attributes->set('started', microtime(true));
    $response = $next($request);          // terusake menyang lapisan sabanjure / controller
    $response->headers->set('X-Time', '...');  // logika "sawise"
    return $response;
}

// routes/web.php  → 4. routing (+ middleware)
Route::get('/items/{id}', [ItemController::class, 'show'])->middleware('auth');

// app/Http/Controllers/ItemController.php  → 6. controller
public function show(int $id)
{
    return response()->json(Item::findOrFail($id));
}
```

## Kenapa iki penting

Lifecycle Laravel dibangun ngubengi **service container** lan **middleware pipeline**, dadi ngerti urutane — bootstrap/provider, banjur global middleware, banjur routing, banjur route middleware, banjur controller, banjur `terminate` — ngandhani sampeyan persis ngendi auth, rate limiting, CORS, lan cleanup manggon. Iki nerangake kenapa sawijining service kudu di-bind ing sawijining provider sadurunge di-inject, kenapa `throttle` nolak sawijining request sadurunge controller sampeyan mlaku, lan kepiye nundha gawean alon menyang terminable middleware supaya pangganggo ora didhihi ngenteni.

Tahap-tahape

Kenapa iki penting

Pitakon sing gegandhengan