Series
Laravel routing looks simple until you hit the middleware ordering bug, the route cache that silently breaks after deploy, or the API versioning scheme that doesn't scale past year one. This series walks through routing the way it actually works in a production app — resource routes, model binding, middleware stacking, caching pitfalls, rate limiting, and testing — each part with real, copy-pasteable code, not just the happy-path example from the docs.
6 parts · about 33 min to read
Laravel routing looks simple until the day you ask "why does this route return a CSRF error" or "why did my API route just lose the user's session." Both questions...
Dasun Kalupahana
5 min read
Laravel route model binding is the reason a resource controller rarely contains a manual Post::findOrFail($id) call. Part 1 covered how Laravel routing works at a basic level, and ended on...
Dasun Kalupahana
4 min read
Laravel middleware is where most "it works locally but not in production" routing bugs hide: a route that should require login but doesn't, a rate limit that counts the wrong...
Dasun Kalupahana
4 min read
Laravel route caching is one of the standard deploy optimizations, and one of the few that can break a site without a single error in your logs: a new page...
Dasun Kalupahana
5 min read
Laravel API versioning is a decision you make once and live with for years, because the first time you rename a field or change a response shape, every client you...
Dasun Kalupahana
6 min read
Laravel rate limiting is easy to switch on and easy to get subtly wrong. A limit that every visitor shares because they all arrive from the load balancer's IP. A...
Dasun Kalupahana
9 min read
We use cookies to improve your experience and analyze traffic. By continuing, you agree to our Privacy Policy.
