Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
MIME-Version: 1.0
References: <0130621f-08da-6519-7570-7ef7cf346d31@Gmail.com> <005e2971-5170-202e-95f2-b814d21f427f@redhat.com>
In-Reply-To: <005e2971-5170-202e-95f2-b814d21f427f@redhat.com>
From: Adrian Brown <adrianbro@gmail.com>
Date: Wed, 13 Dec 2017 09:22:06 +0000
Message-ID: <CAPzWwYo4k36TiM8ekroWTRjHRFA6EkPF-HWmamP3RaMWCxPKcQ@mail.gmail.com>
Subject: Re: Using Topics and Queues for both Java-based and Node.js-based services
To: users@activemq.apache.org
Cc: Jeroen van Ooststroom <j.van.ooststroom@gmail.com>
Content-Type: multipart/alternative; boundary="089e08245348bf0fac0560354d55"
archived-at: Wed, 13 Dec 2017 09:22:22 -0000

--089e08245348bf0fac0560354d55
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think RabbitMQ let=E2=80=99s you map MQTT topics to AMQP  can remember fo=
r sure
but have a look at https://www.rabbitmq.com/mqtt.html

On Wed, 13 Dec 2017 at 8:04 pm, Ulf Lilleengen <lulf@redhat.com> wrote:

> On 12. des. 2017 22:50, Jeroen van Ooststroom wrote:
> > Hello,
> >
> > Coming back to the discussion on the apache-activemq IRC channel of
> > possible Topics and Queues when using ActiveMQ=E2=80=99s MQTT service.
> >
> > First a bit of history then. We=E2=80=99ve have been using multiple Jav=
a-based
> > services for quite a bit of years now utilizing ActiveMQ=E2=80=99s JMS =
Topic and
> > the occasional JMS Queues. Recently, we started expanding by adding a
> > multitude of Node.js-based services to the mix. At some point these
> > services also needed the capability of sending messages. As we already
> > were using ActiveMQ for JMS Messaging with our Java-based services it
> > seemed obvious to stick with ActiveMQ even for our Node.js-based
> > services. However, they can=E2=80=99t leverage JMS evidently. Therefore=
 we
> > picked MQTT and enabled MQTT on our ActiveMQ server next to the already
> > supported JMS. As these Node.js services have been deployed stand-alone
> > up until now, there was no harm in using Topics for this approach.
> >
> > However, we are no looking into deploying these Node.js-based services
> > in a clustered fashion now. (We have an Amazon ECS Cluster to which we
> > want to deploy multiple Containers of the same Node.js-based services.
> > This imposes a problem as for certain messages we only want a single
> > subscriber of a particular service to receive and handle that message.
> > Hence we were leaning towards using Queues instead of Topics for these
> > scenarios. Unfortunately as member dejanb pointed out, MQTT doesn=E2=80=
=99t
> > support Queues.
> >
> > So our question still remains similar. How can we utilize both JMS Topi=
c
> > (1-to-N) and Queue-like (1-to-1) behaviour for both our Java-based and
> > Node.js-based services using ActiveMQ? (We=E2=80=99d like to possible s=
hare
> > these Topics and Queues among the Java- and Node.js-based services.) Is
> > there another approach we should be looking into from a Node.js-based
> > perspective and move away from MQTT and potentially use something
> > different that ActiveMQ provides?
> >
>
> I'm afraid I don't have a good answer on how you can use MQTT, but you
> might want to have a look at using AMQP, which has support for queues,
> topics, JMS clients (qpid-jms[1]) and node.js clients (rhea[2]).
>
> [1] https://qpid.apache.org/components/jms/index.html
> [2] https://github.com/grs/rhea
>
> --
> Ulf
>
--=20
Regards
Adrian Brown

--089e08245348bf0fac0560354d55--