Jobs Laravel Package

Product Decisions This Supports

• Unified Admin Dashboard for Job Management: Integrate job queue monitoring, failed job tracking, and batch processing into Filament’s admin panel, reducing the need for separate tools like Laravel Horizon or Tails.
• Database-Driven Queue Optimization: Replace Redis-based Horizon with a database-backed solution for smaller teams or projects where Redis overhead is unnecessary, improving cost efficiency and simplicity.
• Batch Processing Workflows: Enable Filament users to manage job batches (e.g., bulk exports, data migrations) directly from the UI, reducing manual CLI dependency.
• Failed Job Recovery: Provide a self-service UI for developers/QA to inspect, retry, or delete failed jobs without accessing logs or running commands.
• Roadmap for "No-Code" DevOps: Align with a broader strategy to reduce reliance on Horizon/Tailwind for job management, especially in SaaS products where admin UIs are critical.
• Build vs. Buy: Avoid building custom job management panels from scratch, leveraging Moox’s Filament-native solution to accelerate development.

When to Consider This Package

• Use this if:

  • Your Laravel app uses the database queue driver (not Redis/SQS/Beanstalkd) and needs a Filament-compatible UI for job management.
  • You’re already using Filament and want to consolidate admin tools (e.g., jobs + other Moox packages) under one roof.
  • Your team lacks resources to build a custom job dashboard or maintain Horizon/Tailwind.
  • You prioritize simplicity over advanced Redis features (e.g., real-time monitoring, worker management).
  • You’re evaluating Moox’s ecosystem (e.g., Moox Auth, Moox Media) and want a unified installation process.

• Look elsewhere if:

  • You rely on Redis/SQS/Beanstalkd for queues (Moox Jobs has limited compatibility; see Limitations).
  • You need real-time monitoring or worker management (Horizon/Tailwind are better suited).
  • Your team requires custom job metrics or integrations not supported by Filament’s default UI.
  • You’re using Laravel 10+ with breaking changes not yet reflected in Moox Jobs (check Laravel Version).
  • You prefer open-source alternatives with larger communities (e.g., Laravel Nova, custom Horizon builds).

How to Pitch It (Stakeholders)

For Executives:

"Moox Jobs lets us replace Laravel Horizon with a Filament-native solution for managing job queues, failed jobs, and batches—all from our existing admin panel. This reduces devops overhead, cuts costs (no Redis dependency), and gives our team a self-service tool to debug jobs without CLI access. It’s a lightweight, unified alternative that aligns with our Filament-first strategy, saving ~3–6 months of custom dashboard development."

Key Outcomes:

• Cost Savings: Eliminates Redis infrastructure for database-driven queues.
• Productivity: Filament users (e.g., QA, support) can resolve job issues independently.
• Scalability: Supports batch processing workflows critical for [specific use case, e.g., "nightly data syncs"].

For Engineering:

*"Moox Jobs provides a drop-in Filament plugin for job management, replacing Horizon’s UI with a database-backed solution. It’s ideal if:

• You’re using the database queue driver and want a simpler alternative to Horizon.
• You’re already using Moox’s ecosystem (e.g., Moox Auth) and want a unified moox:install workflow.
• You need basic job monitoring (queues, failures, batches) without real-time features.

Trade-offs:

• No Redis support: Limited to database queues (see Limitations).
• Filament dependency: Requires Filament v2+; not standalone.
• Less mature than Horizon: Smaller community, but MIT-licensed and actively maintained.

Recommendation: Pilot for a non-critical queue (e.g., email processing) to validate UI/UX before full adoption. Pair with Moox’s Jobs for Beginners Guide for onboarding."*