rabbitmq - When is it appropriate to use AMQP? -

rabbitmq - When is it appropriate to use AMQP? -

on previous job used benefits of amqp, not involved in rabbitmq subproject development. on current job want take charge of integrating 1 of amqp implementations (probably rabbitmq). issue here have convinced boss in using amqp.

i reading "rabbitmq in action" , mr. videla wrote amqp improve system, not see how can improve project. utilize 2 servers making api calls in between, not have scalability problem right now. deal real money flows , means need success confirmation operation, i.e. can not set task in queue , "forget" it. benefits amqp bring in case?

could please provide couple real world examples relatively little systems when not need scale hardly? please omit standard "logging" , "broadcast message" situations :)

it sounds need rpc. rabbit not known rpc but does job because:

you can create many messages transactional (ie in 1 transaction) its platform, language , protocol format agnostic (ie send binary over) because of broker thought can add together more servers handle procedures. you can see message flow , rate rabbitmq's admin ui rabbitmq sort of inversion of command @ architecture level in rabbitmq message contract... not procedure. right way it.

now lets compare soap:

soap not give broker or routing severs need know each other. can't tell how annoying have go plugin ip address dev, staging, production. soap not provide transactions. have yourself. soap have utilize xml there more reliable rabbitmq clients soap clients. soap compatibility pita. soap have message , endpoint. in cases pro.

you don't have utilize rabbitmq utilize thought of eventbus/messagebus. not create sort of app out 1 because going pure synchronous rpc asynchronous eventbus/messagebus require lots of work. improve right beginning.

rabbitmq amqp