Sieve Laravel Package

Product Decisions This Supports

• Feature Development: Accelerates implementation of dynamic filtering in APIs/admin panels (e.g., e-commerce product listings, CRM lead pipelines, or analytics dashboards). Reduces boilerplate for common query patterns (e.g., where, orderBy, between).
• Roadmap Prioritization: Ideal for teams building scalable Laravel applications where query complexity grows with feature scope. Justifies investment in maintainable, reusable filtering logic over ad-hoc solutions.
• Build vs. Buy: Avoids reinventing wheel for standard filtering needs (e.g., search, sorting, faceted navigation). Lowers technical debt by leveraging a battle-tested, MIT-licensed package.
• Use Cases:
  • Public APIs with client-driven filtering (e.g., ?color=red&price_min=100).
  • Internal tools requiring dynamic data exploration (e.g., admin dashboards, reporting).
  • Microservices needing consistent query patterns across services.

When to Consider This Package

• Adopt when:

  • Your Laravel app uses Eloquent and requires reusable, declarative filtering (e.g., >5 filterable fields).
  • You prioritize cleaner code over raw SQL flexibility (e.g., replacing nested if/where blocks).
  • Your team lacks bandwidth to build/maintain custom filtering logic from scratch.
  • You need value mapping (e.g., converting request->get('status') to ['active', 'inactive']).
  • Your stakeholders demand faster iteration on filtering features (e.g., MVP launch, A/B testing).

• Look elsewhere if:

  • You need complex joins/subqueries (Sieve focuses on single-model queries).
  • Your filtering logic requires real-time aggregation (e.g., faceted search with counts).
  • You’re using non-Eloquent data sources (e.g., raw database connections, external APIs).
  • Your team prefers full control over SQL generation (e.g., for performance tuning).
  • You’re building a high-scale system where query optimization is critical (benchmark first).

How to Pitch It (Stakeholders)

For Executives: "Sieve lets us ship filtering features 30% faster by eliminating repetitive query logic. For example, instead of writing 20 lines of if statements to handle product filters, we define rules once and reuse them across APIs/admin panels. This reduces dev time, cuts bugs, and keeps our codebase clean—freeing engineers to focus on higher-value work like [insert strategic initiative]. The MIT license and active maintenance (last release: March 2025) ensure long-term reliability."

For Engineers: *"Sieve is a minimalist, Eloquent-first solution for filtering that:

• Dry’s up repetitive where/orderBy logic into reusable filter classes.
• Supports value mapping (e.g., request->status='draft' → ['published_at', null]).
• Integrates seamlessly with Laravel’s request handling (e.g., Filter::apply($request)).
• Weighs <1KB and has zero dependents—no bloat, just functionality.

Example: Replace this:

if ($request->has('category')) { $query->where('category_id', $request->category); }

With this:

$filter = new CategoryFilter($request);
$filter->apply($query);

Perfect for APIs, dashboards, or any Eloquent-heavy app."*