Yaya rayuwar request (request lifecycle) ke aiki a Laravel?

Question

IT Interview Practice · Accepted Answer

Kowace request ɗin Laravel na shiga ta cikin front controller guda ɗaya, `public/index.php`, sannan **HTTP Kernel** ke tuƙa shi ta cikin gungun **middleware** da **router** zuwa **controller**, sannan ya mayar da `Response` — bayan haka **terminable** middleware ke gudana.

## Matakan

```
public/index.php  ── autoload + bootstrap app ɗin
   ▼
HTTP Kernel::handle($request)
   ▼
Bootstrappers  ── env, config, providers (register + boot)
   ▼
Global middleware  ── (TrustProxies, HandleCors, ...)
   ▼
Router dispatch  ── daidaita route
   ▼
Route / group middleware  ── (auth, throttle, verified, ...)
   ▼
Controller (ko closure)  ── logic ɗinka → na mayar da Response
   ▼
Response ──▶ client
   ▼
Kernel::terminate  ── terminable middleware (misali ajiye session, logging)
```

1. **Front controller** — `index.php` na loading Composer autoload sannan ya bootstrap application container.
2. **Kernel::handle** — HTTP Kernel na karɓar `Request` sannan ya gudanar da **bootstrappers**: loading env + config, register da **boot** service providers (nan ne inda framework da bindings ɗinka ke haɗuwa).
3. **Global middleware** — na gudana ga kowace request (CORS, maintenance mode, yanke strings, amincewa da proxy).
4. **Routing** — router na daidaita URI + verb zuwa route.
5. **Route/group middleware** — middleware da aka sanya wa route ko group ɗinsa (`auth`, `throttle`, `verified`) na gudana kafin controller; kowanne na iya toshewa da wuri.
6. **Controller** — action ɗinka (ko route closure) na gudana, na amfani da models/services, sannan ya mayar da `Response` (view, JSON, redirect). Logic ɗin "after" na middleware na gudana yayin da response ke ɓulɓulowa waje.
7. **terminate** — bayan an aika response, `Kernel::terminate` na gudanar da terminable middleware don ayyukan da aka jinkirta.

```php
// app/Http/Middleware/Timing.php  → 3/5. middleware
public function handle($request, Closure $next)
{
    $request->attributes->set('started', microtime(true));
    $response = $next($request);          // wuce zuwa layer na gaba / controller
    $response->headers->set('X-Time', '...');  // logic ɗin "after"
    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));
}
```

## Me ya sa yake da muhimmanci

Rayuwar Laravel an gina ta ne a kewayen **service container** da **middleware pipeline**, don haka sanin tsari — bootstrap/providers, sannan global middleware, sannan routing, sannan route middleware, sannan controller, sannan `terminate` — na gaya maka daidai inda auth, rate limiting, CORS, da tsaftacewa suke. Yana bayyana dalilin da ya sa dole a bind service a cikin provider kafin a inject shi, dalilin da ya sa `throttle` ke ƙin request kafin controller ɗinka ya gudana, da kuma yadda za a jinkirta ayyuka masu jinkiri zuwa terminable middleware domin kada a bar mai amfani yana jira.

Matakan

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa