Architecture for the Message Queue using Rabbit MQ

Question

0.00/5 (No votes)

See more:

Hi All,

I am going to work on the Payment module. The volume of Request my software is going to receive is higher than the volume of requests the third Party Payment Gateway service can handle.

So, I am planning to use the Rabbit MQ for Queuing the Requests. I am not sure how to use it and what should be the architecture for my software with reference to the Message Queue.

Kindly help.

Thanks,
Chris

Posted 20-Apr-15 5:38am

Member 11622800

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

virusstorm · Answer 1 · 2015-04-21T08:22:00

My suggestion is take a simplistic approach. While I have not personally used RabbitMQ, this is a generic queuing approach to this problem.

I would setup a central server (ideally highly available) that all of your other applications or web servers will send messages too. The message should contain the sale amount, payment details, transaction identifier that is unique, source application and source server. Remember that when sending these messages, it needs to be over a secure channel.

On the central server, I would have an application that processes the queue's contents and submit the transactions to your gateway based on the load they are able to handle. This may require a little bit of parallelism. Once you get the response back, you would write the results to another queue. This queue could live on the same server or on the server the message originated from (preferred).

The originating application is then mentoring the response queue for a message with the transaction identifier. This way, it can alert the user on the success or failure.

If this seems too confusing, I can diagram it out for you.

Hope this helps.