Router Laravel Package

Product Decisions This Supports

• Developer Experience (DX) Optimization: Adopting this package enables a cleaner, more declarative routing system, reducing boilerplate in Laravel applications. This aligns with roadmap items focused on developer productivity (e.g., reducing cognitive load for backend engineers) and consistency (e.g., enforcing convention-over-configuration).
• Build vs. Buy: Justifies a "buy" decision for teams already using Laravel, as it eliminates the need to build a custom attribute-based routing system. Ideal for projects where routing complexity is growing (e.g., microservices, modular monoliths) or where adherence to RESTful conventions is critical.
• Use Cases:
  • API-Driven Applications: Simplifies route registration for RESTful APIs, especially with nested resources (e.g., /users/{user}/posts).
  • Legacy System Modernization: Gradually migrates away from manual route definitions in routes/web.php or routes/api.php to attribute-based discovery.
  • Team Scalability: Reduces merge conflicts in route files by decentralizing route definitions to controller classes.
  • Middleware/Authorization: Enables fine-grained middleware assignment at the controller or method level without cluttering route files.

When to Consider This Package

• Adopt When:

  • Your Laravel project has >50 routes and route files are becoming unwieldy.
  • You prioritize convention-over-configuration and want to enforce RESTful patterns.
  • Your team uses PHP 8.3+ and Laravel 13+ (or is planning to upgrade).
  • You need nested resource support (e.g., sub-resources like posts/{post}/comments) without manual route grouping.
  • You want to reduce boilerplate in routes/*.php files while maintaining explicit control over route behavior.
  • Your CI/CD pipeline can handle new dependencies with minimal risk (MIT license, 100% test coverage).

• Look Elsewhere When:

  • You’re using Laravel <13.0 or PHP <8.3 (compatibility constraints).
  • Your routing needs are highly dynamic (e.g., programmatic route generation at runtime).
  • You require advanced route caching or runtime route modification (this package focuses on compile-time discovery).
  • Your team lacks familiarity with PHP attributes or prefers YAML/JSON-based routing (e.g., for non-PHP teams).
  • You need enterprise-grade support (package has no dependents/stars; evaluate risk tolerance).

How to Pitch It (Stakeholders)

For Executives/Stakeholders:

"This package modernizes our Laravel routing system by shifting from manual route definitions to attribute-driven, convention-based discovery. Benefits include:

• Faster Onboarding: New engineers spend less time deciphering route files.
• Reduced Technical Debt: Eliminates duplicate route definitions and enforces RESTful consistency.
• Scalability: Supports nested resources and middleware without bloating routes/*.php.
• Low Risk: MIT-licensed, 100% test coverage, and minimal setup (2 commands to install). For a one-time investment of ~30 minutes to migrate routes, we gain long-term maintainability. Ideal for API-heavy projects or teams growing beyond 5 developers."

For Engineering Teams:

"poshtive/router replaces Laravel’s traditional route registration with PHP attributes, offering:

• Zero Boilerplate: Annotate controllers/methods (e.g., @Route, @Get, @Middleware) instead of defining routes in files.
• Strict Safety: Detects duplicate routes and skips invalid ones during bootstrapping.
• Flexibility: Supports explicit HTTP verbs, model binding, and inheritance-aware discovery.
• Future-Proof: Aligns with Laravel’s evolution (PHP 8.3+, Laravel 13+). Migration path: Start with a single controller, validate behavior, then roll out incrementally. Tradeoff: Slight learning curve for attributes, but pays off in cleaner codebases."