<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IoT on Dejan Bosanac</title>
    <link>/categories/iot/</link>
    <description>Recent content in IoT on Dejan Bosanac</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
    <lastBuildDate>Mon, 17 Aug 2015 00:00:00 +0000</lastBuildDate><atom:link href="/categories/iot/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Messaging for IoT</title>
      <link>/posts/2015-08-17-messaging-for-iot/</link>
      <pubDate>Mon, 17 Aug 2015 00:00:00 +0000</pubDate>
      
      <guid>/posts/2015-08-17-messaging-for-iot/</guid>
      <description>&lt;p&gt;Deploying message broker for an IoT use case introduces some new challenges to the broker scalability. We&amp;rsquo;re talking now about thousands of connections, consumers and destinations, which make us think of how we provision, configure and monitor our messaging infrastructure much more carefully. In this post I&amp;rsquo;ll try to sum up some of techniques that can be used with the current Apache ActiveMQ in terms to scale it better for IoT deployment. I&amp;rsquo;ll also describe some of the new features we developed for the 5.12.0 release to make it a better fit in this new world. And finally I&amp;rsquo;ll try to explain where we can go from here and what can we work on in the future.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
