In my opinion the greatest power and flexibility comes when running the broker standalone. Then you can scale up if necessary (e.g. "horizontally" via clustering or "vertically" via better hardware), configure high availability, easily add support for other protocols, etc. without having to deal with an application layer that's tied to the broker. Then your applications (e.g. your MQTT devices, your project running in Wildfly, etc.) can access the broker however they need.
Justin On Thu, May 23, 2019 at 1:23 PM Rafael Fernandez <rferl...@gmail.com> wrote: > Hi Justin. > > Let me a last question. > > The idea of useing Wildfly as an application server comes from a personal > project I developed a couple of years ago. It was a JEE application > software > for tracking vehicles. The comunication with tracking devices was based on > Web services. Now the trend in tracking devices in Mqtt so I am thinking > about to migrate my project from web services to mqtt. > > I would like to know your opinion, wether I should use Wildfly Artemis as a > MOM or it would be better to use Artemis standalone and subscribe to it > from > my project running in Wildfly > > Regards > > Rafael > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
