CloudAMQP
CloudAMQP’s configurations follow the same model as RabbitMQ’s with a point of attention to the HostName parameter that already includes the url and credentials provided when creating the service in CloudAMQP. User/Password/Port parameters are not required
Subscribe to a queue in RabbitMQ
The JSON below demonstrates the default configuration with the RabbitMQ credentials, the exchange used, the Retry, the Fallback, the Threads, and the ‘Subscribe’ option to receive events in the ‘orderevents’ queue as defined in the Queues item.
|
|
In the example below, we’re detailing the default Adapter settings and the RabbitMQ-specific settings.
General | — |
---|---|
Enable | Enable the Stream adapter (True/False) |
Alias | Defines a unique name to identify the service |
Default | Sets as default to the centary of having more than one Stream (True/False) |
StreamType | Sets the Stream type (RabbitMQ/Kafka) |
HostName | Configures the url/credential provided by CloudAMQP |
Exchange | Sets up the default RabbitMQ |
ExchangeType | Configures the type of Exchange |
Retry | Configure the number of retries |
Fallback | Configures a State for automatic resitence in case of failure |
Threads | Sets the number of concurrent connections processing events |
Buffer | Defines the number of events obtained per connection |
Subscribe | Configures RabbitMQ Queues for Read |
Example in the application log with this configuration:
|
|
YAML example with application settings:
To export the configurations as an environment variable and use in Kubernetes, run the command in the Devprime CLI:
dp export kubernetes
|
|
Last modified January 10, 2024 (967dcac3)Use the RabbitMQ examples to explore other variations in configuration.