RMQ Scenarios

Change Events

A service that needs to publish change events for a domain.

An example of this would be a security directory that receives a change request for a user account, to change its username. This update would need to be propagated to other services that use or cache the user’s username, and to client devices that display it.

In such a case, the security directory can publish the change event to a fanout exchange, and subscribers can deal with it appropriately.

• Caches can invalidate the appropriate record

 

RPC Requests

Cloud services that make requests needing deterministic responses use RPC over RMQ.

An implementation of this has been integration tested in the libraries, and provides an abstraction similar to a local method call.

See this for details: RabbitMQ Cloud Service RPC Conventions