Dispatcher Laravel Package

Product Decisions This Supports

• Upgrade and roadmap planning: Hyperf v3.2.0 is a breaking-change release requiring PHP >=8.2, Carbon v3 behavior changes, logger/cache configuration restructuring, async queue method renaming, and removal of deprecated APIs. PM should decide whether to schedule migration now or pin existing services to v3.1.x until a migration window is approved.
• Platform modernization: Adds PHP 8.4 readiness, Symfony 6/7 support, PHPUnit 11, Elasticsearch 8.x/9.x, SQL Server database support, PDO subclass support, and modern PHP 8.4 array/JSON utilities. This supports roadmap items that depend on current framework, search, database, and testing ecosystem versions.
• Async processing and scale: New async queue consumer auto-registration and per-job queue naming reduce boilerplate for background jobs, queue isolation, and multi-tenant or workload-specific processing.
• Developer productivity and operability: StdoutLogger timestamps, event listener caching, Collection/Arr utilities, Pipeline finally(), Context Macroable, and NonCoroutine testing support improve supportability and reduce custom utility code.
• Build vs buy: For teams already on Hyperf, upgrading is usually preferable to maintaining a fork. For new high-concurrency PHP services, evaluate Hyperf against Laravel Octane/Swoole/RoadRunner based on coroutine maturity, team skills, and operational readiness.
• Risk management: Logger/cache config changes and Carbon behavior changes can affect running services. Allocate explicit migration, regression testing, and staged rollout budget rather than treating v3.2.0 as a routine patch.

When to Consider This Package

• Consider adoption/upgrade when: you run Hyperf v3.x services and need PHP 8.4 readiness, Elasticsearch 8/9, SQL Server, modern Symfony/PHPUnit dependencies, or improved async queue process management.
• Strong fit when: the product has high-concurrency PHP workloads such as API gateways, microservices, websocket services, async job processing, or persistent-worker applications where coroutine runtime is a real advantage.
• Team fit: engineering has coroutine/Swoole/Swow experience and can safely review config migrations, dependency constraints, queue behavior, and Carbon edge cases.
• Look elsewhere when: the team is Laravel-first without coroutine expertise, the product is a simple CRUD app served well by standard Laravel queues, services run on PHP below 8.2, or the organization requires a low-breaking-change LTS path.
• Migration caution: v3.2.0 is not a drop-in patch. Validate Carbon timestamp/timezone and diffInDays() behavior, logger/cache config structures, async queue getQueueName() to getPoolName() changes, Swow ResponseEmitterInterface registration, removed deprecated interfaces, and PHP 8.4 CSV escape parameters.

How to Pitch It (Stakeholders)

• Executives: Hyperf v3.2.0 modernizes the PHP platform with PHP 8.2+/8.4 support, Elasticsearch 8/9, SQL Server, and performance/observability improvements. It keeps our stack supported and reduces custom boilerplate, but it requires a planned migration because of breaking changes.
• Engineering: plan a migration spike and staged rollout. Key work includes dependency upgrades, Carbon behavior review, logger and cache config rewrites, async queue method renames, Swow dependency configuration, and regression tests for removed deprecated APIs.
• Product: prioritize the upgrade if the roadmap depends on Elasticsearch 8/9, SQL Server, PHP 8.4, or async queue scale. Otherwise pin v3.1.x, schedule the upgrade after the current release, and budget for migration and regression testing. Success measures include reduced queue boilerplate, supported dependency versions, improved log traceability, and fewer custom framework workarounds.