這篇文章主要介紹了AMQP-RabbitMQ中RPC模式和關(guān)注消息處理結(jié)果的示例分析，具有一定借鑒價(jià)值，感興趣的朋友可以參考下，希望大家閱讀完這篇文章之后大有收獲，下面讓小編帶著大家一起了解一下。

梁子湖ssl適用于網(wǎng)站、小程序/APP、API接口等需要進(jìn)行數(shù)據(jù)傳輸應(yīng)用場景，ssl證書未來市場廣闊！成為創(chuàng)新互聯(lián)的ssl證書銷售渠道，可以享受市場價(jià)格4-6折優(yōu)惠！如果有意向歡迎電話聯(lián)系或者加微信：18982081108（備注：SSL證書合作）期待與您的合作！

6. RPC

But what if we need to run a function on a remote computer and wait for the result? Well, that's a different story. This pattern is commonly known as Remote Procedure Call or RPC.

大概意思是說，上面幾種模式都是生產(chǎn)者將消息發(fā)送到Rabbitmq，然后就不管了，也不管是否有消費(fèi)者進(jìn)行了消費(fèi)，也不管消費(fèi)的結(jié)果是怎樣的。上面幾種場景已經(jīng)可以滿足大多數(shù)需求。但是有一種場景是生產(chǎn)者必須知道消費(fèi)結(jié)果才能進(jìn)行后續(xù)操作，

• 圖示

• Our RPC will work like this:

• For an RPC request, the Client sends a message with two properties: replyTo, which is set to a anonymous exclusive queue created just for the request, and correlationId, which is set to a unique value for every request.

• The request is sent to an rpc_queue queue.

• The RPC worker (aka: server) is waiting for requests on that queue. When a request appears, it does the job and sends a message with the result back to the Client, using the queue from the replyTo field.

• The client waits for data on the reply queue. When a message appears, it checks the correlationId property. If it matches the value from the request it returns the response to the application.

感謝你能夠認(rèn)真閱讀完這篇文章，希望小編分享的“AMQP-RabbitMQ中RPC模式和關(guān)注消息處理結(jié)果的示例分析”這篇文章對大家有幫助，同時(shí)也希望大家多多支持創(chuàng)新互聯(lián)，關(guān)注創(chuàng)新互聯(lián)行業(yè)資訊頻道，更多相關(guān)知識等著你來學(xué)習(xí)!