- What is micro-module/job-queue and how does it differ from Laravel's built-in queue?
- micro-module/job-queue is a lightweight job queue module designed for Laravel applications built as micro-modules, aiming to keep job dispatch and processing within module boundaries. It claims to plug into Laravel's existing queue system rather than replace it, but the TPM assessment warns it may be redundant if it merely re-implements native queue primitives. Its core value is organizational encapsulation for modular monoliths, not raw throughput or new features. Developers should confirm whether it implements Laravel's queue contracts or forks them before adopting.
- How do I install micro-module/job-queue in a Laravel application?
- Install it via Composer using composer require micro-module/job-queue, then check if it auto-registers a service provider or requires manual registration in config/app.php. Review composer.json for Laravel and PHP version constraints, and publish any config files if the package provides a config publish tag. Because there are zero dependents, validate the installation in a sandbox branch before touching production code.
- Which Laravel and PHP versions does micro-module/job-queue support?
- The provided context does not list exact Laravel and PHP version constraints, so you must inspect the package's composer.json for require entries. The TPM assessment specifically flags version constraints as a gate, including whether it supports your Laravel version and PHP runtime. Do not assume compatibility based on the description alone; test installation in an isolated environment first.
- Does micro-module/job-queue work with Laravel Horizon, Telescope, and queue:work?
- Interoperability with Horizon, Telescope, and the queue:work or queue:listen commands depends on whether the package implements Laravel's native queue contracts or delegates to existing drivers. The TPM assessment lists this as a key question and notes that it may not interoperate if it rolls its own queue primitives. You should run a spike to verify that jobs appear in Horizon, are traceable in Telescope, and process correctly under standard workers.
- How does micro-module/job-queue handle retries, failures, and dead-letter queues?
- The package description mentions enterprise queue features like distributed job execution, unique jobs, sub jobs, and dependent jobs, but the provided context does not detail retry, failure, or dead-letter semantics. The TPM assessment warns that queue semantics are deceptively hard and that a re-implementation is more likely to get at-least-once delivery, visibility timeouts, and poison-pill handling wrong. You must review the source and write tests for retries, failures, and worker restarts before trusting it in production.
- Can I use micro-module/job-queue in production given its low adoption?
- The TPM assessment rates technical risk as high: the package has zero stars, zero dependents, a single maintainer, and no evidence of production use outside the maintainer. Job processing is critical-path infrastructure, so a silent abandonment or correctness bug could become a production incident. If you proceed, pin the version, review the source, wrap it behind an internal interface, and run a side-by-side spike against Laravel's native driver before committing.
- How do I test jobs dispatched through micro-module/job-queue?
- Start by checking whether the package ships with CI, test coverage, static analysis, and a changelog, as the TPM assessment flags these as key questions. In your own test suite, use Laravel's Queue::fake() if the package integrates with native queue contracts, or otherwise mock the package's dispatcher and assert job payloads. Add integration tests that exercise retries, failures, and worker shutdown in a sandbox environment.
- What are the alternatives to micro-module/job-queue for modular Laravel applications?
- Laravel's native queue system with database, Redis, SQS, or Beanstalkd drivers is the default alternative and includes mature retries, backoff, failure handling, batching, and Horizon observability. For modular monoliths, you can achieve module ownership by organizing job classes and connections per module without a third-party package. If you need unique or dependent jobs, consider first-party batching or community packages with proven adoption rather than an unproven module.
- Is micro-module/job-queue actively maintained and what is its release cadence?
- The TPM assessment notes a single maintainer, no visible contributor base, and only one recent release (April 2025) as a positive but single data point. There is no changelog or release cadence information in the provided context, so you should inspect the repository's commit history, issues, and tagged releases. Given the bus factor risk, treat maintenance commitment as unproven and have a fallback plan to native Laravel queues.
- Does micro-module/job-queue support unique jobs, sub jobs, and dependent jobs?
- The package overview claims distributed job execution, unique jobs, sub jobs, and dependent jobs, which are advanced features beyond Laravel's basic queue API. However, the TPM assessment cautions that the package may simply re-implement Laravel primitives, so you need to verify whether these features are robust, tested, and compatible with native drivers. Review the source and write spike tests for uniqueness locks, sub-job chaining, and dependency resolution before relying on them.