[aerogear-dev] AeroGear Messaging

[Burr Sutter]

We already have ActiveMQ, a message broker that will deal with things like “durable subscriptions”, holding messages until the subscriber wakes up and acknowledges receipt.  

There is also Mosca as a Node.js-based MQTT focused message broker.  

There will be a wide spectrum of Things - from most distributed edge sensors with energy harvesting (smart dust)  to robust “gateway” servers that look a lot like your typical datacenter server today.   It is currently unclear to me which of the application protocols will “win”.  At this moment, MQTT is a winner (great support from numerous vendors) and I feel that CoAP will be a winner as well. 
AMQP or DDS may win on the beefier gateways but not so much edge intelligent things.


> On Apr 21, 2015, at 10:22 AM, Summers Pittman <supittma at redhat.com> wrote:
> 
> 
> 
> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> more something like a unified messanger platform, where we have real messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP etc while having support for push notifications as well.
> We could probably extend the Push API. I mean it already does half the work for us ;)
> 
> That would be nice to have, at some point
> 
> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> like Notifier?
> 
> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman <supittma at redhat.com <mailto:supittma at redhat.com>> wrote:
> So IoT is getting a lot of attention within the company (or at least within my monkeysphere).  From the demo project I've noticed that a lot of the work is in messaging and message handling.  What do you guys think about exploring this space more?  How does it / can it /should it fit into our roadmap?
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/c2cb70a9/attachment-0001.html