Ruby amqp updating client properties
The Gradle build script at the end of this tutorial will automatically generate the required SEMP Java Client Library for the first time if it doesn’t exist yet, as part of the build.
Before jumping to specific tasks like creating a Client Username, we will first introduce a few basic concepts common to the SEMP client library.
For some high end setups, getting the last drop of performance and scalability from the cluster is an advanced task and might include strategies which need more logic on the client side: By default, every queue created on Rabbit MQ is created on one node (the queue master) and is replicated to other nodes to achieve high availability.
In certain cases, high availability is sacrificed to avoid the overhead of replication to achieve higher performance.
The Rabbit MQ service enforces some limitations to ensure the cluster’s performance.
There is extensive support for creating SEMP client APIs in many programming languages.
You can learn more about the SEMP API using the Online Documentation.
These documents explain the API concepts and details about the REST API.
If you are interested in using the API directly through HTTP, you can look at this Quick Start tutorial which walks you through the basics of making SEMP calls directly through HTTP.
The examples below make a few assumptions for simplicity: The Generating the SEMP Client Library tutorial provides details about generating the latest version of the library.