When is it appropriate to use AMQP?

In my previous work, I took advantage of AMQP, but I did not participate in the development of rabbitMQ subprojects. In my current work, I want to take responsibility for the integration of one of the AMQP implementations (possibly rabbitMQ). The problem here is that I have to convince my boss to use AMQP.

I read RabbitMQ in Action, and Mr. Videla wrote that AMQP can improve any system, but I don’t see how I can improve my project. We use only 2 servers making API calls between them, so we do not have a scalability problem right now. We are dealing with real cash flows, and this means that we need confirmation of success for any operation, i.e. I cannot queue a task and forget about it. What are the benefits of AMQP in this case?

Could you provide a couple of real-world examples for relatively small systems when you don't need to scale? Please leave the standard "logging" and "broadcast messages" of the situation :)

+5
source share
1 answer

, RPC. RPC , :

  • (.. )
  • , (.. )
  • - .
  • RabbitMQ admin UI
  • RabbitMQ - .
  • RabbitMQ - ... . .

: SOAP:

  • SOAP , . , , IP- dev, staging, production.
  • SOAP . .
  • SOAP, XML
  • RabbitMQ, SOAP. SOAP - PITA.
  • SOAP . .

RabbitMQ eventbus/messagebus. - , RPC eventbus/messagebus . .

+6

All Articles