Mzunguko wa maisha wa request unafanyaje kazi katika Laravel?

Question

IT Interview Practice · Accepted Answer

Kila request ya Laravel huingia kupitia front controller mmoja, `public/index.php`, huendeshwa na **HTTP Kernel** kupitia rundo la **middleware** na **router** kwenda **controller**, na hurejesha `Response` — baada yake middleware ya **terminable** huendeshwa.

## Hatua

```
public/index.php  ── autoload + bootstrap app
   ▼
HTTP Kernel::handle($request)
   ▼
Bootstrappers  ── env, config, providers (register + boot)
   ▼
Global middleware  ── (TrustProxies, HandleCors, ...)
   ▼
Router dispatch  ── linganisha route
   ▼
Route / group middleware  ── (auth, throttle, verified, ...)
   ▼
Controller (au closure)  ── mantiki yako → hurejesha Response
   ▼
Response ──▶ client
   ▼
Kernel::terminate  ── terminable middleware (mfano hifadhi session, logging)
```

1. **Front controller** — `index.php` hupakia Composer autoload na kufanya bootstrap ya container ya application.
2. **Kernel::handle** — HTTP Kernel hupokea `Request` na kuendesha **bootstrappers**: kupakia env + config, kusajili na **boot** service providers (hapa ndipo framework na bindings zako huunganishwa).
3. **Global middleware** — huendeshwa kwa kila request (CORS, hali ya matengenezo, kupunguza strings, kuamini proxy).
4. **Routing** — router hulinganisha URI + verb na route.
5. **Route/group middleware** — middleware iliyopewa route au group yake (`auth`, `throttle`, `verified`) huendeshwa kabla ya controller; kila moja inaweza kukatiza.
6. **Controller** — action yako (au route closure) huendeshwa, hutumia models/services, na hurejesha `Response` (view, JSON, redirect). Mantiki ya "baada" ya middleware huendeshwa response inaporudi nje.
7. **terminate** — baada ya response kutumwa, `Kernel::terminate` huendesha terminable middleware kwa kazi zilizoahirishwa.

```php
// app/Http/Middleware/Timing.php  → 3/5. middleware
public function handle($request, Closure $next)
{
    $request->attributes->set('started', microtime(true));
    $response = $next($request);          // pitisha kwa tabaka linalofuata / controller
    $response->headers->set('X-Time', '...');  // mantiki ya "baada"
    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));
}
```

## Kwa nini ni muhimu

Mzunguko wa maisha wa Laravel umejengwa kuzunguka **service container** na **middleware pipeline**, kwa hivyo kujua mpangilio — bootstrap/providers, kisha global middleware, kisha routing, kisha route middleware, kisha controller, kisha `terminate` — hukuambia hasa mahali auth, rate limiting, CORS, na usafishaji vinapokaa. Hueleza kwa nini service lazima ibind katika provider kabla ya kuinjectwa, kwa nini `throttle` hukataa request kabla ya controller yako kuendeshwa, na jinsi ya kuahirisha kazi ya polepole kwenda terminable middleware ili mtumiaji asisubiri.

Hatua

Kwa nini ni muhimu

Maswali yanayohusiana