- What is micro-module/enqueue used for in Laravel?
- It is a lightweight Laravel package from the micro-module family that provides a simple way to enqueue jobs and dispatch work onto queues, integrating with Laravel's queue system. Its stated goal is to keep background processing tidy and configurable. However, the repository is a read-only fork with zero stars and no dependents, so treat its capabilities as unverified until you review the source.
- How do I install micro-module/enqueue?
- Install it with Composer, for example composer require micro-module/enqueue, and pin the exact version in composer.json because there is only a single recent release. It is MIT licensed and has no obvious private dependencies, so nominal install cost is low. First confirm the service provider registration and PHP/Laravel compatibility from the source, then run your own contract tests against your broker.
- Does micro-module/enqueue wrap php-enqueue/enqueue or reimplement transports?
- That is not established from the provided description, and the name overlap with php-enqueue/enqueue is only a signal, not proof. You must read the source to determine whether it is a thin framework-integration layer over a transport or a bespoke queue implementation. The answer changes your risk profile, because a wrapper inherits upstream fixes while a reimplementation does not.
- Which queue transports and brokers does micro-module/enqueue support?
- The provided context does not document supported drivers, so do not assume AMQP, Redis, or SQS support. Review the source and README to confirm which transport interfaces and container bindings exist. Then test a publish/consume round-trip against your target broker before planning any rollout.
- Which Laravel and PHP versions does micro-module/enqueue support?
- The supported PHP and Laravel version matrix is not stated, and no CI matrix is mentioned in the evaluation. The package has a single release dated 2024-10-25, so recent does not mean maintained or proven across framework majors. Pin the exact version and validate it against your PHP and Laravel matrix in CI before adopting.
- Is micro-module/enqueue safe for production use?
- It carries high technical risk: bus factor of one, zero stars and dependents, no external production validation, and unclear provenance. Treat it as unproven and restrict it to a low-blast-radius async workload such as notifications or audit fan-out, never revenue-path messaging. Run broker-loss, poison-message, and redelivery drills and require maintainer responsiveness plus a fork plan before expanding scope.
- Does micro-module/enqueue support retries, backoff, and dead-letter queues?
- The context does not say whether retries, backoff, DLQ, or idempotency hooks are implemented in the package or delegated to the broker or Laravel's queue. Confirm delivery semantics, at-least-once versus at-most-once, and message serialization format from the source. Write contract tests for retry, DLQ, poison message, and broker reconnect, and treat the package's own tests as insufficient.
- What are the alternatives to micro-module/enqueue?
- Laravel's first-party Illuminate\Queue with Redis or SQS, plus Horizon, is the default comparator and is maintained by the framework vendor. If you need a broker abstraction outside Laravel's queue, php-enqueue/enqueue is the credible upstream to evaluate. For a Laravel app already running Horizon, this package has a high bar to justify itself given zero adoption.
- How is micro-module/enqueue maintained and what is the bus factor?
- It is published under the single-organization temafey namespace with one release, zero stars, zero dependents, and no community migration stories. The bus factor is one, and a single recent release is not a track record. The highest-probability failure is not a runtime bug but the package breaking on a PHP or Laravel major upgrade with nobody obligated to fix it.
- How hard is it to remove micro-module/enqueue later?
- Plan for adopt, don't marry: define your own MessageBus or QueueClient interface and place this package behind it as one adapter. Then swapping to Laravel's queue or php-enqueue becomes a single-file change instead of a codebase-wide rip-out. Pin the version, keep contract tests you own, and measure the rip-out cost before expanding scope.