activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Bertram <>
Subject Re: .Net Rest services integration with ActiveMQ
Date Tue, 24 Oct 2017 14:13:25 GMT
This is a really broad question that would probably be better answered via
a consulting service of some kind.  That said, I'll attempt a concise

I think the first thing you'd want to do is figure out which message broker
you are going to use - ActiveMQ 5.x or ActiveMQ Artemis.  Involved in that
decision will be what protocol and/or API you want to use for en-queuing
and de-queuing messages.  Both brokers support JMS 1.1, AMQP, STOMP, &
MQTT.  Artemis adds JMS 2 support.

Once you've decided on a broker and protocol then you'll need to write your
application endpoints.  How you write your endpoints will be dictated by
the protocol/API you choose.  In general, though you'll want your "REST
service" to send a message to the broker and then you'd create some
consumers to receive those messages and then work with the database.

You can find lots of good tutorials and/or examples online for just about
any protocol/API you choose to work with.


On Tue, Oct 24, 2017 at 8:46 AM, bhattacharyyasom <> wrote:

> Hello,
> I have the following scenario that i want to address using queuing. I am
> not
> very sure if this is feasible though.
> So today i have a .NET rest services developed on the WebAPI interface that
> receives JSON messages and calls different database procedures with that
> parsed data.
> Recently i came across a situation where under heavy stress we are getting
> database connection timeout issues. I want to setup a scenario that does
> the
> following,
> i.The JSON request comes in to the Rest service.
> ii.The Rest service sends down the parsed data to the MQ .
> iii.Have a way to call the database procedures by reading from this parsed
> data.
> Can someone guide me through how to start/proceed with this work ?
> --
> Sent from:
> f2341805.html

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message