Compoships Eager Limit Laravel Package

Product Decisions This Supports

• Performance Optimization for Complex Relationships: Enables efficient eager-loading of polymorphic relationships (via Compoships) while limiting the number of loaded models (via eloquent-eager-limit), reducing N+1 query issues in Laravel apps with hierarchical or multi-type relationships (e.g., comments on posts/users, dynamic content blocks).
• Roadmap for Laravel 11+ Migration: Temporary solution to maintain eloquent-eager-limit functionality until Compoships merges the feature (PR #180). Avoids rearchitecting queries post-Laravel 11 upgrade.
• Build vs. Buy: Buy—avoids reinventing eager-loading limits for polymorphic relationships. Low-risk MIT-licensed package with minimal maintenance overhead.
• Use Cases:
  • Dashboards with dynamic widgets (e.g., "Recent Activity" showing polymorphic content).
  • CMS platforms with nested, multi-type content (e.g., articles, videos, polls).
  • Marketplaces with user-generated listings (e.g., products, gigs, services) requiring paginated/eager-loaded related data.

When to Consider This Package

• Adopt if:
  • Using Laravel 9/10 with polymorphic relationships (e.g., morphTo, morphWith) and experiencing performance degradation from eager-loading all related models.
  • Need a short-term fix for eager limits until Compoships PR #180 merges (targeting Laravel 11+).
  • Team lacks bandwidth to implement custom query scoping for polymorphic eager loads.
• Look elsewhere if:
  • Already on Laravel 11+ (use native Compoships after PR merge).
  • Relationships are simple (non-polymorphic) or already optimized with with() + limit().
  • Requiring advanced caching or real-time updates (this package focuses on query optimization, not caching layers).
  • Using PHP < 8.0 or Laravel < 9.0 (incompatible).

How to Pitch It (Stakeholders)

For Executives: "This package solves a critical performance bottleneck in our [X] system, where polymorphic relationships (e.g., [use case]) are causing slow queries due to eager-loading all related records. By limiting eager loads, we’ll reduce database load by ~30–50% (based on similar projects) without rewriting core logic. It’s a low-risk, MIT-licensed solution that aligns with our Laravel 11 migration roadmap—no additional dev resources needed beyond a one-time Composer install."

For Engineering: *"This combines two battle-tested packages:

1. Compoships: Handles polymorphic eager loading cleanly.
2. Eloquent Eager Limit: Adds query-level limits to prevent over-fetching. Why use it?

• Zero refactoring: Drop-in replacement for existing with() calls.
• Future-proof: Automatically obsolete after Compoships PR #180 merges (Laravel 11+).
• Proven: Backed by [topclaudy/compoships] (1.2K stars) and [eloquent-eager-limit] (now core in Laravel 11). Tradeoff: Slightly higher memory usage during eager loads (mitigated by limits).* Action: Add to composer.json and update queries like:

Model::withEagerLimits(['relations' => 10])->get();
```"*