agatanga/relay
Composer 安装命令:
composer require agatanga/relay
包简介
A better way to create complex batch job queues in Laravel.
关键字:
README 文档
README
A better way to create and manage complex batch job queues in Laravel:
Relay::chain([new Job1, new Job2]) ->batch([new Job3_1, new Job3_2]) ->chain([new Job4, new Job5]) ->through([new Middleware]) ->dispatch();
Main features
- Relay doesn't create/modify DB tables
- Clean looking complex batches
- Ability to set middleware for multiple jobs
- Search for specific batch via metadata
- Monitor batch progress
- Search for failed jobs
Installation
composer require agatanga/relay
Usage Examples
Flatten nested callbacks
Here is a flattened batches written with Relay:
use Agatanga\Relay\Facades\Relay; Relay::chain('Downloading', [ new DownloadSources($project), new DetectSettings($project), ]) ->then('Updating project data', [ new ReadStringFiles($project), new ReadSourceFiles($project), ]) ->then('Updating project data', [ new FixFalseUnusedStrings($project), ]) ->finally('Cleaning up', [ new IgnoreKnownStrings($project), new RemoveSources($project), ]) ->through(new Middleware($project)) ->dispatch();
View the same code written without Relay
Bus::batch([ [ new DownloadSources($project)->through(new Middleware($project)), new DetectSettings($project)->through(new Middleware($project)), ], ])->then(function (Batch $batch) use ($project) { Bus::batch([ new ReadStringFiles($project)->through(new Middleware($project)), new ReadSourceFiles($project)->through(new Middleware($project)), ])->then(function (Batch $batch) use ($project) { Bus::batch([ new FixFalseUnusedStrings($project)->through(new Middleware($project)), ])->finally(function (Batch $batch) use ($project) { Bus::batch([ new IgnoreKnownStrings($project)->through(new Middleware($project)), new RemoveSources($project)->through(new Middleware($project)), ])->name('Cleaning up')->dispatch(); })->name('Updating project data')->dispatch(); })->name('Updating project data')->dispatch(); })->name('Downloading')->dispatch();
Middleware
Relay allows you to set middleware for multiple jobs:
Relay::chain([new Job1, new Job2]) ->batch([new Job3_1, new Job3_2]) ->chain([new Job4, new Job5], [new Middleware1]) ->chain([new Job6, new Job7]) ->through([new Middleware2]) // middleware for Job1-3, Job6-7 ->dispatch();
Metadata
Before we start, you may want to know that Relay doesn't modify job_batches table
to store metadata. All data is stored inside the name column and limited to
255 chars. Here is how the name of the batch may look like with the metadata:
Cleaning up|[project:58][project.update:58][3/3]
Now, let's see how to use meta method to store additional information:
use Agatanga\Relay\Facades\Relay; Relay::chain([ new DownloadSources($project), new DetectSettings($project), ]) ->then([ new ReadStringFiles($project), new ReadSourceFiles($project), ]) ->finally([ new IgnoreKnownStrings($project), new RemoveSources($project), ]) ->name('Update Project (:current of :total)') ->meta('project.update', $project->id) ->meta('causer', auth()->user()->id) ->dispatch();
Then search for the batch and retrieve metadata value or name of the batch:
use Agatanga\Relay\Facades\Relay; Relay::whereMeta('causer', $userId)->all(); Relay::whereMeta('project', $id)->first()->meta('causer'); Relay::whereMeta('project.update', $id)->first()->name; // returns clean name
Progress
Let's assume that the search query from the section above returned the first
batch (then and finally callbacks are not yet started). Relay takes this into
account and will return the progress within 0-33% range.
use Agatanga\Relay\Facades\Relay; Relay::whereMeta('project.update', $id)->first()->progress; // only the last callback can return 100%
Failed Jobs
When batch job fails, Laravel adds a failed job record to the failed_jobs table.
Relay allows you to retrieve these failed jobs:
use Agatanga\Relay\Facades\Relay; Relay::whereMeta('project.update', $id)->first()->failedJobs(); // or get the exception string of the last failed job $batch = Relay::whereMeta('project.update', $id)->first(); if ($batch->failed) { echo $batch->exception; }
agatanga/relay 适用场景与选型建议
agatanga/relay 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 37 次下载、GitHub Stars 达 11, 最近一次更新时间为 2021 年 09 月 15 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「queue」 「laravel」 「queue manager」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 agatanga/relay 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 agatanga/relay 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 agatanga/relay 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
The file manager intended for using Laravel with CKEditor / TinyMCE / Colorbox
PHP AMQP Binding Library
A Laravel package to monitor queue jobs.
KCFinder web file manager
Publish / Subscribe / Event Manager
Message queue statistics for OroPlatform
统计信息
- 总下载量: 37
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 11
- 点击次数: 7
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2021-09-15