Request Lifecycle for Laravels
The Laravel request lifecycle is the path an HTTP request follows from public/index.php through the HTTP kernel and middleware to a route, controller and finally a response. Understanding it explains where routes, controllers and Blade views fit, and where you can intercept a request with middleware.
Stage: Foundations · Part of the Laravel roadmap · Last reviewed 19 November 2026
What to learn in Request Lifecycle
- Define routes in routes/web.php with parameters and names
- Write controllers, including resource controllers, that return views or responses
- Render data in Blade templates using layouts, components and directives
- Attach middleware to routes and explain the order in which it runs
- Generate URLs from named routes instead of hard coding paths
Request Lifecycle interview questions
What is middleware in Laravel?
Middleware is code that wraps a request, running before and sometimes after the route handler. It is used for tasks like authentication, CSRF protection and rate limiting. Each middleware either passes the request on to the next layer or returns a response early.
What is the difference between Blade components and includes?
An include inserts another view and shares the parent data. A Blade component is a reusable unit with its own class or anonymous template, explicit props and slots, which makes inputs clear and the markup easier to test and reuse across pages.
Where Request Lifecycle fits in the Laravel roadmap
Request Lifecycle belongs to the Foundations stage (beginner level), which takes about 20 hours. The Laravel way.
Other units in this stage
Back to the full Laravel roadmap