2019-12-12 16:24:04 +08:00
|
|
|
|
# AMQP 組件
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
[hyperf/amqp](https://github.com/hyperf/amqp) 是實現 AMQP 標準的組件,主要適用於對 RabbitMQ 的使用。
|
2019-03-30 22:53:32 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
## 安裝
|
2019-03-30 22:53:32 +08:00
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
composer require hyperf/amqp
|
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
## 默認配置
|
2019-10-14 15:16:53 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| 配置 | 類型 | 默認值 | 備註 |
|
2019-10-14 15:16:53 +08:00
|
|
|
|
|:----------------:|:------:|:---------:|:--------------:|
|
|
|
|
|
| host | string | localhost | Host |
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| port | int | 5672 | 端口號 |
|
2019-10-14 15:16:53 +08:00
|
|
|
|
| user | string | guest | 用户名 |
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| password | string | guest | 密碼 |
|
2019-10-14 15:16:53 +08:00
|
|
|
|
| vhost | string | / | vhost |
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| concurrent.limit | int | 0 | 同時消費的數量 |
|
|
|
|
|
| pool | object | | 連接池配置 |
|
2019-10-14 15:16:53 +08:00
|
|
|
|
| params | object | | 基本配置 |
|
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```php
|
2019-03-08 12:04:46 +08:00
|
|
|
|
<?php
|
|
|
|
|
|
|
|
|
|
return [
|
|
|
|
|
'default' => [
|
|
|
|
|
'host' => 'localhost',
|
|
|
|
|
'port' => 5672,
|
|
|
|
|
'user' => 'guest',
|
|
|
|
|
'password' => 'guest',
|
|
|
|
|
'vhost' => '/',
|
2019-10-14 15:16:53 +08:00
|
|
|
|
'concurrent' => [
|
|
|
|
|
'limit' => 1,
|
|
|
|
|
],
|
2019-03-08 12:04:46 +08:00
|
|
|
|
'pool' => [
|
|
|
|
|
'min_connections' => 1,
|
|
|
|
|
'max_connections' => 10,
|
|
|
|
|
'connect_timeout' => 10.0,
|
|
|
|
|
'wait_timeout' => 3.0,
|
|
|
|
|
'heartbeat' => -1,
|
|
|
|
|
],
|
|
|
|
|
'params' => [
|
|
|
|
|
'insist' => false,
|
|
|
|
|
'login_method' => 'AMQPLAIN',
|
|
|
|
|
'login_response' => null,
|
|
|
|
|
'locale' => 'en_US',
|
|
|
|
|
'connection_timeout' => 3.0,
|
2020-04-30 17:09:23 +08:00
|
|
|
|
'read_write_timeout' => 6.0,
|
2019-03-08 12:04:46 +08:00
|
|
|
|
'context' => null,
|
|
|
|
|
'keepalive' => false,
|
2019-12-04 16:54:31 +08:00
|
|
|
|
'heartbeat' => 3,
|
2020-06-16 01:43:41 +08:00
|
|
|
|
'close_on_destruct' => false,
|
2019-03-08 12:04:46 +08:00
|
|
|
|
],
|
|
|
|
|
],
|
2019-07-04 01:49:07 +08:00
|
|
|
|
'pool2' => [
|
|
|
|
|
...
|
|
|
|
|
]
|
2019-03-08 12:04:46 +08:00
|
|
|
|
];
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
可在 `producer` 或者 `consumer` 的 `__construct` 函數中, 設置不同 `pool`.
|
2019-07-04 01:49:07 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
## 投遞消息
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
使用 `gen:producer` 命令創建一個 `producer`
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
|
|
|
|
```bash
|
2019-03-08 12:04:46 +08:00
|
|
|
|
php bin/hyperf.php gen:amqp-producer DemoProducer
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
在 DemoProducer 文件中,我們可以修改 `@Producer` 註解對應的字段來替換對應的 `exchange` 和 `routingKey`。
|
|
|
|
|
其中 `payload` 就是最終投遞到消息隊列中的數據,所以我們可以隨意改寫 `__construct` 方法,只要最後賦值 `payload` 即可。
|
2019-03-08 12:04:46 +08:00
|
|
|
|
示例如下。
|
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
> 使用 `@Producer` 註解時需 `use Hyperf\Amqp\Annotation\Producer;` 命名空間;
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```php
|
2019-03-08 12:04:46 +08:00
|
|
|
|
<?php
|
|
|
|
|
|
|
|
|
|
declare(strict_types=1);
|
|
|
|
|
|
|
|
|
|
namespace App\Amqp\Producers;
|
|
|
|
|
|
|
|
|
|
use Hyperf\Amqp\Annotation\Producer;
|
|
|
|
|
use Hyperf\Amqp\Message\ProducerMessage;
|
|
|
|
|
use App\Models\User;
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* DemoProducer
|
|
|
|
|
* @Producer(exchange="hyperf", routingKey="hyperf")
|
|
|
|
|
*/
|
|
|
|
|
class DemoProducer extends ProducerMessage
|
|
|
|
|
{
|
|
|
|
|
public function __construct($id)
|
|
|
|
|
{
|
2019-12-12 16:24:04 +08:00
|
|
|
|
// 設置不同 pool
|
2019-07-04 01:49:07 +08:00
|
|
|
|
$this->poolName = 'pool2';
|
|
|
|
|
|
2019-03-08 12:04:46 +08:00
|
|
|
|
$user = User::where('id', $id)->first();
|
|
|
|
|
$this->payload = [
|
|
|
|
|
'id' => $id,
|
|
|
|
|
'data' => $user->toArray()
|
|
|
|
|
];
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:41:17 +08:00
|
|
|
|
通過 DI Container 獲取 `Hyperf\Amqp\Producer` 實例,即可投遞消息。以下實例直接使用 `ApplicationContext` 獲取 `Hyperf\Amqp\Producer` 其實並不合理,DI Container 具體使用請到 [依賴注入](zh-hk/di.md) 章節中查看。
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```php
|
2019-03-08 12:04:46 +08:00
|
|
|
|
<?php
|
|
|
|
|
use Hyperf\Amqp\Producer;
|
|
|
|
|
use App\Amqp\Producers\DemoProducer;
|
|
|
|
|
use Hyperf\Utils\ApplicationContext;
|
|
|
|
|
|
|
|
|
|
$message = new DemoProducer(1);
|
|
|
|
|
$producer = ApplicationContext::getContainer()->get(Producer::class);
|
|
|
|
|
$result = $producer->produce($message);
|
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
## 消費消息
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
使用 `gen:amqp-consumer` 命令創建一個 `consumer`。
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
|
|
|
|
```bash
|
2019-03-08 12:04:46 +08:00
|
|
|
|
php bin/hyperf.php gen:amqp-consumer DemoConsumer
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
在 DemoConsumer 文件中,我們可以修改 `@Consumer` 註解對應的字段來替換對應的 `exchange`、`routingKey` 和 `queue`。
|
|
|
|
|
其中 `$data` 就是解析後的消息數據。
|
2019-03-08 12:04:46 +08:00
|
|
|
|
示例如下。
|
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
> 使用 `@Consumer` 註解時需 `use Hyperf\Amqp\Annotation\Consumer;` 命名空間;
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```php
|
2019-03-08 12:04:46 +08:00
|
|
|
|
<?php
|
|
|
|
|
|
|
|
|
|
declare(strict_types=1);
|
|
|
|
|
|
|
|
|
|
namespace App\Amqp\Consumers;
|
|
|
|
|
|
|
|
|
|
use Hyperf\Amqp\Annotation\Consumer;
|
|
|
|
|
use Hyperf\Amqp\Message\ConsumerMessage;
|
|
|
|
|
use Hyperf\Amqp\Result;
|
2021-06-28 09:13:15 +08:00
|
|
|
|
use PhpAmqpLib\Message\AMQPMessage;
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* @Consumer(exchange="hyperf", routingKey="hyperf", queue="hyperf", nums=1)
|
|
|
|
|
*/
|
|
|
|
|
class DemoConsumer extends ConsumerMessage
|
|
|
|
|
{
|
2021-06-28 09:13:15 +08:00
|
|
|
|
public function consumeMessage($data, AMQPMessage $message): string
|
2019-03-08 12:04:46 +08:00
|
|
|
|
{
|
|
|
|
|
print_r($data);
|
|
|
|
|
return Result::ACK;
|
|
|
|
|
}
|
|
|
|
|
}
|
2019-03-19 14:52:21 +08:00
|
|
|
|
```
|
2019-03-08 12:04:46 +08:00
|
|
|
|
|
2020-01-10 16:49:10 +08:00
|
|
|
|
### 禁止消費進程自啟
|
|
|
|
|
|
|
|
|
|
默認情況下,使用了 `@Consumer` 註解後,框架會自動創建子進程啟動消費者,並且會在子進程異常退出後,重新拉起。
|
|
|
|
|
如果出於開發階段,進行消費者調試時,可能會因為消費其他消息而導致調試不便。
|
|
|
|
|
|
|
|
|
|
這種情況,只需要在 `@Consumer` 註解中配置 `enable=false` (默認為 `true` 跟隨服務啟動)或者在對應的消費者中重寫類方法 `isEnable()` 返回 `false` 即可
|
|
|
|
|
|
|
|
|
|
```php
|
|
|
|
|
<?php
|
|
|
|
|
|
|
|
|
|
declare(strict_types=1);
|
|
|
|
|
|
|
|
|
|
namespace App\Amqp\Consumers;
|
|
|
|
|
|
|
|
|
|
use Hyperf\Amqp\Annotation\Consumer;
|
|
|
|
|
use Hyperf\Amqp\Message\ConsumerMessage;
|
|
|
|
|
use Hyperf\Amqp\Result;
|
2021-06-28 09:13:15 +08:00
|
|
|
|
use PhpAmqpLib\Message\AMQPMessage;
|
2020-01-10 16:49:10 +08:00
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* @Consumer(exchange="hyperf", routingKey="hyperf", queue="hyperf", nums=1, enable=false)
|
|
|
|
|
*/
|
|
|
|
|
class DemoConsumer extends ConsumerMessage
|
|
|
|
|
{
|
2021-06-28 09:13:15 +08:00
|
|
|
|
public function consumeMessage($data, AMQPMessage $message): string
|
2020-01-10 16:49:10 +08:00
|
|
|
|
{
|
|
|
|
|
print_r($data);
|
|
|
|
|
return Result::ACK;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public function isEnable(): bool
|
|
|
|
|
{
|
|
|
|
|
return parent::isEnable();
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
```
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
2020-04-30 17:09:23 +08:00
|
|
|
|
### 設置最大消費數
|
|
|
|
|
|
|
|
|
|
可以修改 `@Consumer` 註解中的 `maxConsumption` 屬性,設置此消費者最大處理的消息數,達到指定消費數後,消費者進程會重啟。
|
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
### 消費結果
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
框架會根據 `Consumer` 內的 `consume` 方法所返回的結果來決定該消息的響應行為,共有 4 中響應結果,分別為 `\Hyperf\Amqp\Result::ACK`、`\Hyperf\Amqp\Result::NACK`、`\Hyperf\Amqp\Result::REQUEUE`、`\Hyperf\Amqp\Result::DROP`,每個返回值分別代表如下行為:
|
2019-10-07 23:47:41 +08:00
|
|
|
|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| 返回值 | 行為 |
|
2019-10-14 15:16:53 +08:00
|
|
|
|
|------------------------------|----------------------------------------------------------------------|
|
2019-12-12 16:24:04 +08:00
|
|
|
|
| \Hyperf\Amqp\Result::ACK | 確認消息正確被消費掉了 |
|
|
|
|
|
| \Hyperf\Amqp\Result::NACK | 消息沒有被正確消費掉,以 `basic_nack` 方法來響應 |
|
|
|
|
|
| \Hyperf\Amqp\Result::REQUEUE | 消息沒有被正確消費掉,以 `basic_reject` 方法來響應,並使消息重新入列 |
|
|
|
|
|
| \Hyperf\Amqp\Result::DROP | 消息沒有被正確消費掉,以 `basic_reject` 方法來響應 |
|
2020-05-19 11:26:54 +08:00
|
|
|
|
|
|
|
|
|
## RPC 遠程過程調用
|
|
|
|
|
|
|
|
|
|
除了典型的消息隊列場景,我們還可以通過 AMQP 來實現 RPC 遠程過程調用,本組件也為這個實現提供了對應的支持。
|
|
|
|
|
|
|
|
|
|
### 創建消費者
|
|
|
|
|
|
|
|
|
|
RPC 使用的消費者,與典型消息隊列場景的消費者實現基本無差,唯一的區別是需要通過調用 `reply` 方法返回數據給生產者。
|
|
|
|
|
|
|
|
|
|
```php
|
|
|
|
|
<?php
|
|
|
|
|
|
|
|
|
|
declare(strict_types=1);
|
|
|
|
|
|
|
|
|
|
namespace App\Amqp\Consumer;
|
|
|
|
|
|
|
|
|
|
use Hyperf\Amqp\Annotation\Consumer;
|
|
|
|
|
use Hyperf\Amqp\Message\ConsumerMessage;
|
|
|
|
|
use Hyperf\Amqp\Result;
|
|
|
|
|
use PhpAmqpLib\Message\AMQPMessage;
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* @Consumer(exchange="hyperf", routingKey="hyperf", queue="rpc.reply", name="ReplyConsumer", nums=1, enable=true)
|
|
|
|
|
*/
|
|
|
|
|
class ReplyConsumer extends ConsumerMessage
|
|
|
|
|
{
|
|
|
|
|
public function consumeMessage($data, AMQPMessage $message): string
|
|
|
|
|
{
|
|
|
|
|
$data['message'] .= 'Reply:' . $data['message'];
|
|
|
|
|
|
|
|
|
|
$this->reply($data, $message);
|
|
|
|
|
|
|
|
|
|
return Result::ACK;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
### 發起 RPC 調用
|
|
|
|
|
|
|
|
|
|
作為生成者發起一次 RPC 遠程過程調用也非常的簡單,只需通過依賴注入容器獲得 `Hyperf\Amqp\RpcClient` 對象並調用其中的 `call` 方法即可,返回的結果是消費者 reply 的數據,如下所示:
|
|
|
|
|
|
|
|
|
|
```php
|
|
|
|
|
<?php
|
|
|
|
|
use Hyperf\Amqp\Message\DynamicRpcMessage;
|
|
|
|
|
use Hyperf\Amqp\RpcClient;
|
|
|
|
|
use Hyperf\Utils\ApplicationContext;
|
|
|
|
|
|
|
|
|
|
$rpcClient = ApplicationContext::getContainer()->get(RpcClient::class);
|
|
|
|
|
// 在 DynamicRpcMessage 上設置與 Consumer 一致的 Exchange 和 RoutingKey
|
|
|
|
|
$result = $rpcClient->call(new DynamicRpcMessage('hyperf', 'hyperf', ['message' => 'Hello Hyperf']));
|
|
|
|
|
|
|
|
|
|
// $result:
|
|
|
|
|
// array(1) {
|
|
|
|
|
// ["message"]=>
|
|
|
|
|
// string(18) "Reply:Hello Hyperf"
|
|
|
|
|
// }
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
### 抽象 RpcMessage
|
|
|
|
|
|
|
|
|
|
上面的 RPC 調用過程是直接通過 `Hyperf\Amqp\Message\DynamicRpcMessage` 類來完成 Exchange 和 RoutingKey 的定義,並傳遞消息數據,在生產項目的設計上,我們可以對 RpcMessage 進行一層抽象,以統一 Exchange 和 RoutingKey 的定義。
|
|
|
|
|
|
|
|
|
|
我們可以創建對應的 RpcMessage 類如 `App\Amqp\FooRpcMessage` 如下:
|
|
|
|
|
|
|
|
|
|
```php
|
|
|
|
|
<?php
|
|
|
|
|
use Hyperf\Amqp\Message\RpcMessage;
|
|
|
|
|
|
|
|
|
|
class FooRpcMessage extends RpcMessage
|
|
|
|
|
{
|
|
|
|
|
|
|
|
|
|
protected $exchange = 'hyperf';
|
|
|
|
|
|
|
|
|
|
protected $routingKey = 'hyperf';
|
|
|
|
|
|
|
|
|
|
public function __construct($data)
|
|
|
|
|
{
|
|
|
|
|
// 要傳遞數據
|
|
|
|
|
$this->payload = $data;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
2020-06-16 01:43:41 +08:00
|
|
|
|
這樣我們進行 RPC 調用時,只需直接傳遞 `FooRpcMessage` 實例到 `call` 方法即可,無需每次調用時都去定義 Exchange 和 RoutingKey。
|