In order to ease the transition between new applications, it may sometimes be necessary for business teams to coordinate services and processes using services that cannot communicate in real-time. PlaidCloud provides a high performance messaging queue to handle asynchronous communication, with a wide range of delivery options, including:
This function is provided by RabbitMQ clusters and is not intended to replace internal message queueing systems, although PlaidCloud’s message queue is capable of doing so.
Click here (https://www.rabbitmq.com/tutorials/tutorial-two-python.html) for additional information from RabbitMQ.
Virtual Hosts (vHosts) can be thought of as small, isolated message servers used for specific purposes such as queues, exchanges, and bindings. PlaidCloud uses vHosts to form its foundation for the message broker infrastructure.
To view current vHosts:
This will open the vHosts Table in the workspace, which includes vHost information and access to Queues, Permissions, Bindings, and Exchanges related to the vHost.
To create a vHost:
Once the vHost is created, it will be tagged with its reference to a workspace identifier. For example, if you create a vHost with the name of ‘super’ and its identifier is 890, the actual name of the user will be ‘cloud_890_super’. This allows for unique vHosts without constant name collisions.
To delete a vHost:
Note: Deleting a vHost will delete all of its associated permissions, bindings, queues, and exchanges.
To reach and view vHost Queues:
This will open the Queues Table which displays the list of queues and other important information related to the vHost, including its message state, consumers, and rate of message processing.
To create a queue:
This will open a form where you can provide a name, durability level, and determine if the queue should be deleted when no consumers are present.
Durability is useful if a message needs to be retained in the event of a system failure or restart. If you choose not to create a durable queue, then the message will be lost after a restart. Although durability is useful, it is not always desired.
Creating a durable queue results in a slightly slower process because each message must be stored in permanent storage. We suggest then that you only create a durable queue when the message is critical and use non-durable queues when a message is executed right away or is not critical.
To delete a queue:
Note: When a queue is deleted, any consumers listening on the queue will be disconnected from the queue.
Purging a queue will delete all messages in that queue.
Note: Messages that have already been acknowledged will not be purged because at least one member has received and marked the message as incomplete.
To purge a queue:
To view exchanges:
This will open the Exchanges Table which displays the list of all exchanges related to the vHost.
To create an exchange:
To delete an exchange:
To view bindings:
This will open the Bindings Table, which displays the list of bindings and other important information related to the vHost.
To create a binding:
To delete bindings:
To view permissions:
This will open the Permissions Table, which displays the list of users and their permissions related to the vHost.
To create a permission:
To delete permissions:
In order to access messages in the message queue, you must first set up users. PlaidCloud allows you to create an unlimited number of users in order to suit your needs.
Note: Because users can be granted permission to access multiple vHosts without needing different access levels, it is unnecessary to create one user for every vHost.
To view users who may access vHost and messaging services:
This will open the User Table, which displays users currently in the workspace and their admin level permissions.
To create a new user:
Note: You cannot edit any of the settings, including the password, after creating the user.
The Admin Level setting provides the user with different privileges. PlaidCloud provides three levels of access:
No Admin Access provides no administrative access but allows the user to utilize all other permission based access.
Management Admin Access provides full permission based access, as well as the following:
Monitoring Admin Access provides everything “Management Admin Access” provides, as well as the following:
To delete a user:
Note: Deleting a user will automatically remove all permissions granted to the user on all vHosts.