Conas a oibríonn saolré an request in Laravel?

Question

IT Interview Practice · Accepted Answer

Téann gach request Laravel isteach trí aon front controller amháin, `public/index.php`, tiomáintear é ag an **HTTP Kernel** trí chruach **middleware** agus an **router** chuig **controller**, agus filleann sé `Response` — agus ina dhiaidh sin ritheann middleware **terminable**.

## Na céimeanna

```
public/index.php  ── autoload + bootstrap an app
   ▼
HTTP Kernel::handle($request)
   ▼
Bootstrappers  ── env, config, providers (register + boot)
   ▼
Global middleware  ── (TrustProxies, HandleCors, ...)
   ▼
Router dispatch  ── meaitseáil route
   ▼
Route / group middleware  ── (auth, throttle, verified, ...)
   ▼
Controller (nó closure)  ── do loighic → filleann Response
   ▼
Response ──▶ client
   ▼
Kernel::terminate  ── terminable middleware (m.sh. sábháil session, logging)
```

1. **Front controller** — luchtaíonn `index.php` an Composer autoload agus bootstrap-álann sé container na feidhmchláir.
2. **Kernel::handle** — faigheann an HTTP Kernel an `Request` agus ritheann sé na **bootstrappers**: luchtaigh env + config, register agus **boot** na service providers (is é seo an áit a snaidhmtear an framework agus do bindings le chéile).
3. **Global middleware** — ritheann sé do gach request (CORS, mód cothabhála, teaghráin a bhearradh, muinín proxy).
4. **Routing** — meaitseálann an router an URI + verb chuig route.
5. **Route/group middleware** — ritheann middleware a shanntar don route nó dá ghrúpa (`auth`, `throttle`, `verified`) roimh an controller; is féidir le gach ceann acu ciorcadghearradh.
6. **Controller** — ritheann do action (nó route closure), úsáideann sé models/services, agus filleann sé `Response` (view, JSON, redirect). Ritheann loighic "tar éis" an middleware agus an response ag boilgeadh amach arís.
7. **terminate** — tar éis an response a sheoladh, ritheann `Kernel::terminate` an middleware terminable le haghaidh obair iarchurtha.

```php
// app/Http/Middleware/Timing.php  → 3/5. middleware
public function handle($request, Closure $next)
{
    $request->attributes->set('started', microtime(true));
    $response = $next($request);          // cuir ar aghaidh chuig an gcéad chiseal / controller eile
    $response->headers->set('X-Time', '...');  // loighic "tar éis"
    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));
}
```

## Cén fáth a bhfuil sé tábhachtach

Tá saolré Laravel tógtha timpeall an **service container** agus an **middleware pipeline**, mar sin nuair a bhíonn a fhios agat an t-ord — bootstrap/providers, ansin global middleware, ansin routing, ansin route middleware, ansin controller, ansin `terminate` — insíonn sé duit go beacht cá bhfuil auth, teorannú ráta, CORS, agus glanadh ina gcónaí. Míníonn sé cén fáth a gcaithfear service a bind i provider sula n-injecteáiltear é, cén fáth a ndiúltaíonn `throttle` request roimh do controller a rith, agus conas obair mhall a iarchur chuig terminable middleware ionas nach gcoinnítear an t-úsáideoir ag fanacht.

Na céimeanna

Cén fáth a bhfuil sé tábhachtach

Ceisteanna gaolmhara