baohan/swoole-gearman
Composer 安装命令:
composer require baohan/swoole-gearman
包简介
A multi-processes worker framework based on Swoole and Gearman
README 文档
README
A multi-processes worker framework based on Swoole.
Install
$ composer require baohan/swoole-gearman
But you should set runtime infrastructure up with specified version of swoole, gearman and php first.
Run by Docker
> docker pull baohanddd/swoole-gearman:1.6.1
> docker pull artefactual/gearmand
> docker network create swoole-gearman
> docker run --rm --name=gearman --network=swoole-gearman artefactual/gearmand
> cd your_project/
> docker run --rm --name=worker --network=swoole-gearman -v=$(pwd):/data -w=/data baohanddd/swoole-gearman:1.6.1 php server.php
How
Quick start
It's a simple server, we run the server and start some workers are waiting for next job.
use baohan\SwooleGearman\Collection; use baohan\SwooleGearman\Server; use Monolog\Logger; require('vendor/autoload.php'); try { $s = new Server(Logger::INFO); $s->worker_num = 1; $s->task_worker_num = 19; $s->addCallback('timestamp::print', function () { return new class() extends \baohan\SwooleGearman\Job { public function execute(Collection $payload, int $workerId): bool { sleep(1); echo "worker[{$workerId}] => ".$payload['message'].PHP_EOL; return true; } }; }); $s->start(); } catch (Throwable $e) { echo $e->getMessage(); }
The server will be started.
[2021-08-20 05:52:59] swoole-gearman.INFO: server starting... {"host":"127.0.0.1","port":9500,"worker_num":1,"task_worker_num":19,"task_max_request":500} []
Let's write a simple client:
use Swoole\Client; $client = new Client(SWOOLE_SOCK_TCP); if (!$client->connect('127.0.0.1', 9500, 0.5)) { echo "connect failed. Error: {$client->errCode}\n"; } $data = [ 'name' => 'timestamp::print', 'data' => [ 'message' => '' ] ]; for ($i = 0; $i < 1024; $i++) { $data['data']['message'] = 'query on '.$i; $client->send(json_encode($data)); echo $client->recv(); } $client->close();
The results
......
worker[11] => query on 1019
worker[15] => query on 1023
worker[14] => query on 1022
worker[9] => query on 1017
worker[5] => query on 1013
worker[8] => query on 1016
worker[4] => query on 1012
worker[2] => query on 1010
worker[13] => query on 1021
worker[12] => query on 1020
worker[7] => query on 1015
......
Now we try post job into Gearman Job server.
To do that, just need replace \baohan\SwooleGearman\Server to \baohan\SwooleGearman\Gearman.
please take a look, there isn't need task_worker_num option yet, host and port are same with gearman-job-server.
use baohan\SwooleGearman\Collection; use Monolog\Logger; require('vendor/autoload.php'); try { $s = new \baohan\SwooleGearman\Gearman(Logger::INFO); $s->worker_num = 10; $s->host = 'gearman'; $s->port = '4730'; $s->addCallback('timestamp::print', function () { return new class() extends \baohan\SwooleGearman\Job { public function execute(Collection $payload, int $workerId): bool { sleep(1); echo "worker[{$workerId}] => ".$payload['message'].PHP_EOL; return true; } }; }); $s->start(); } catch (Throwable $e) { echo $e->getMessage(); }
On client side, we post job to gearman server instead of swoole server by gearman client.
<?php $gmc = new GearmanClient(); $gmc->addServer('gearman', '4730'); $data = [ 'name' => 'timestamp::print', 'data' => [ 'message' => '' ] ]; for ($i = 0; $i < 1024; $i++) { $data['data']['message'] = $i + 1; $gmc->doBackground('timestamp::print', json_encode($data)); if ($gmc->returnCode() != GEARMAN_SUCCESS) { echo "bad return code".PHP_EOL; exit; } }
In this mode, The huge advantage is never lose jobs even worker server is crashed, all jobs are stored in Gearman. On the other side, all clients only need to know gearman server address and port, we can deploy more than one instances of swoole server on difference machines more easily.
That's all.
baohan/swoole-gearman 适用场景与选型建议
baohan/swoole-gearman 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 518 次下载、GitHub Stars 达 0, 最近一次更新时间为 2016 年 08 月 23 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「redis」 「php」 「gearman」 「worker」 「swoole」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 baohan/swoole-gearman 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 baohan/swoole-gearman 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 baohan/swoole-gearman 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Microservice RPC through message queues.
Message Queue solutions for Magento2. Supports RabbitMQ, AMQP, STOMP, Amazon SQS, Kafka, Redis, Google PubSub, Gearman, Beanstalk, Google PubSub
The CodeIgniter Redis package
Adds gearman support to your Symfony2 or Symfony3 project
贝嘟分布式缓存扩展
Redis distributed locks for laravel
统计信息
- 总下载量: 518
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 15
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2016-08-23