Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3DC11200D24 for ; Tue, 24 Oct 2017 16:13:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3C6F3160BE0; Tue, 24 Oct 2017 14:13:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 82C44160BDB for ; Tue, 24 Oct 2017 16:13:34 +0200 (CEST) Received: (qmail 36139 invoked by uid 500); 24 Oct 2017 14:13:28 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 36128 invoked by uid 99); 24 Oct 2017 14:13:28 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2017 14:13:28 +0000 Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 809DA1A0029 for ; Tue, 24 Oct 2017 14:13:27 +0000 (UTC) Received: by mail-oi0-f54.google.com with SMTP id m198so37085944oig.5 for ; Tue, 24 Oct 2017 07:13:26 -0700 (PDT) X-Gm-Message-State: AMCzsaVuIJAcPGjB5IwgkRYA9ToGhKS7M6N0Ard0hOLFL7WegZ8KvRr7 2oV40ahjrZmNBkhF7JH+M9wqNMBbf4u8bLdOwrhzSQ== X-Google-Smtp-Source: ABhQp+TDOHqZVtll8+nYB4a1eQvi/N4Ij3IiSNCWBhRPz61NSIvIGbkAoAdar8HGbauI8KMOC5icphrP68slC4LM42c= X-Received: by 10.157.0.214 with SMTP id 22mr9119829otk.327.1508854405497; Tue, 24 Oct 2017 07:13:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.139.53 with HTTP; Tue, 24 Oct 2017 07:13:25 -0700 (PDT) In-Reply-To: <1508852765355-0.post@n4.nabble.com> References: <1508852765355-0.post@n4.nabble.com> From: Justin Bertram Date: Tue, 24 Oct 2017 09:13:25 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: .Net Rest services integration with ActiveMQ To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="94eb2c1c19d0dbb62e055c4b8a91" archived-at: Tue, 24 Oct 2017 14:13:35 -0000 --94eb2c1c19d0dbb62e055c4b8a91 Content-Type: text/plain; charset="UTF-8" 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 answer. 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. Justin On Tue, Oct 24, 2017 at 8:46 AM, bhattacharyyasom < bhattacharyyasom@gmail.com> 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: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html > --94eb2c1c19d0dbb62e055c4b8a91--