The PHP AMQPExchange::bind API performs a focused operation on an object or value. The examples below show its effect on actual data.
Binds an exchange to another exchange using a routing key.
What Is AMQPExchange::bind in PHP?
Binds an exchange to another exchange using a routing key.
This API requires a relevant extension or PHP version and cannot be reflected in the local PHP 8.4 runtime. Refer to the version or extension note below before using the examples.
Compatibility note: Install the PECL AMQP extension and configure a RabbitMQ-compatible broker before running this example.
Example 1: Basic Usage
This example uses a small input to make the main behavior visible.
<?php
$connection = new AMQPConnection([
"host" => getenv("AMQP_HOST") ?: "127.0.0.1",
"port" => 5672,
"login" => getenv("AMQP_USERNAME") ?: "guest",
"password" => getenv("AMQP_PASSWORD") ?: "guest"
]);
$connection->connect();
$channel = new AMQPChannel($connection);
$exchange = new AMQPExchange($channel);
$exchange->setName("events.exchange");
$exchange->setType(AMQP_EX_TYPE_DIRECT);
$exchange->declareExchange();
$sourceExchange = new AMQPExchange($channel);
$sourceExchange->setName("source.exchange");
$sourceExchange->setType(AMQP_EX_TYPE_DIRECT);
$sourceExchange->declareExchange();
$exchange->bind($sourceExchange->getName(), "events.created");
$connection->disconnect();
Binds an exchange to another exchange using a routing key.
Example 2: A Different Input
A different set of values shows the same operation in another situation.
<?php
$connection = new AMQPConnection([
"host" => getenv("AMQP_HOST") ?: "127.0.0.1",
"port" => 5672,
"login" => getenv("AMQP_USERNAME") ?: "guest",
"password" => getenv("AMQP_PASSWORD") ?: "guest"
]);
$connection->connect();
$channel = new AMQPChannel($connection);
$exchange = new AMQPExchange($channel);
$exchange->setName("audit.exchange");
$exchange->setType(AMQP_EX_TYPE_DIRECT);
$exchange->declareExchange();
$sourceExchange = new AMQPExchange($channel);
$sourceExchange->setName("source.exchange");
$sourceExchange->setType(AMQP_EX_TYPE_DIRECT);
$sourceExchange->declareExchange();
$exchange->bind($sourceExchange->getName(), "events.created");
$connection->disconnect();
Declaring, binding and publishing require a reachable broker and adequate permissions; publishing is not equivalent to consumer acknowledgment.
Practical Example: Applying the Feature
This example shows an application-style use of the feature, with its surrounding setup visible.
<?php
$connection = new AMQPConnection([
"host" => getenv("AMQP_HOST") ?: "127.0.0.1",
"port" => 5672,
"login" => getenv("AMQP_USERNAME") ?: "guest",
"password" => getenv("AMQP_PASSWORD") ?: "guest"
]);
$connection->connect();
$channel = new AMQPChannel($connection);
$exchange = new AMQPExchange($channel);
$exchange->setName("jobs.exchange");
$exchange->setType(AMQP_EX_TYPE_DIRECT);
$exchange->declareExchange();
$sourceExchange = new AMQPExchange($channel);
$sourceExchange->setName("source.exchange");
$sourceExchange->setType(AMQP_EX_TYPE_DIRECT);
$sourceExchange->declareExchange();
$exchange->bind($sourceExchange->getName(), "events.created");
$connection->disconnect();
The code is shown for learning. Adjust the class names, inputs and error handling to suit your application.
Important Behavior and Edge Cases
- Declaring, binding and publishing require a reachable broker and adequate permissions; publishing is not equivalent to consumer acknowledgment.
- Binds an exchange to another exchange using a routing key.
- Observe differences in empty inputs, invalid states and optional extension availability where relevant.
Comparison With Related Approaches
| Approach | Important Difference |
|---|---|
AMQPExchange::bind | Binds an exchange to another exchange using a routing key. |
| AMQPQueue | Exchanges route publications according to bindings; queues retain deliveries until consumers handle them. |
Common Beginner Mistakes
| Mistake | Correct Approach |
|---|---|
Ignoring the documented state or precondition of AMQPExchange::bind | Declaring, binding and publishing require a reachable broker and adequate permissions; publishing is not equivalent to consumer acknowledgment. |
| Expecting a different type of result | Read the declared return type and distinguish returned values from changes to the source object. |
| Assuming a related API works identically | Exchanges route publications according to bindings; queues retain deliveries until consumers handle them. |
Key Takeaways
- Binds an exchange to another exchange using a routing key.
- Declaring, binding and publishing require a reachable broker and adequate permissions; publishing is not equivalent to consumer acknowledgment.
- Use the example that matches the values, runtime version and dependencies in your application.
AMQPExchange::bind is useful when its behavior matches the data structure and lifecycle of your PHP application. Choose it with a clear understanding of its preconditions and returned values.