<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thomas A. Valletta on Medium]]></title>
        <description><![CDATA[Stories by Thomas A. Valletta on Medium]]></description>
        <link>https://medium.com/@tvalletta?source=rss-515ed559018b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*BXzH8LV0ZM7bfgE0.jpeg</url>
            <title>Stories by Thomas A. Valletta on Medium</title>
            <link>https://medium.com/@tvalletta?source=rss-515ed559018b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:05:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tvalletta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Web Console for Nats Streaming Server]]></title>
            <link>https://medium.com/@tvalletta/a-web-console-for-nats-streaming-server-1c5363a058da?source=rss-515ed559018b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c5363a058da</guid>
            <category><![CDATA[nat]]></category>
            <category><![CDATA[nats-streaming]]></category>
            <category><![CDATA[kuali]]></category>
            <category><![CDATA[nats-streaming-console]]></category>
            <category><![CDATA[hack-week]]></category>
            <dc:creator><![CDATA[Thomas A. Valletta]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 15:04:06 GMT</pubDate>
            <atom:updated>2018-01-15T15:04:06.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NwHYafnBIxtsIcLL0IOj7A.png" /></figure><p>At <a href="http://kuali.co/">Kuali</a> we have begun to use <a href="https://nats.io/documentation/streaming/nats-streaming-intro/">Nats Streaming Server</a> to pass messages between services and to keep a persistent log of events. Most of the time it works great, but on occasion a message does not arrive where it is expected. In these circumstances we needed a little more insight into what clients were connected and to which channels they were subscribed. To make our troubleshooting easier I spent my hackweek creating a tool that I creatively called “Nats Streaming Console”.</p><p>The console can be pointed to any Nats Streaming Server that is configured to expose monitoring data. It shows configuration detail about the server, the data store, connected clients and channels. When a channel or subscription is selected within the tool, the most recent messages are live streamed to the web console using Web Sockets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaSMu3gltt5XIiMcAobbtQ.png" /></figure><p>The message details are presented using react-json-tree so that large JSON structures have syntax highlighting and can be expanded for easier navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFMGtjBqTvlb6ES3VzUfEg.png" /></figure><p>The tool is MIT licensed and available on <a href="https://github.com/KualiCo/nats-streaming-console">github</a>. It can be run on a developer workstation and pointed to a Nats Streaming Server on the local machine or in a production environment. To make deployment easier, a Dockerfile is included with the source and a public Docker image will be available soon. I also built the console into an Electron application, but because this is my first foray into Electron, it only works on my machine. :( As soon as I figure out what I am doing wrong, I will make the Electron application available as well.</p><p>I hope you find the tool valuable!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c5363a058da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Nats Streaming Server?]]></title>
            <link>https://medium.com/@tvalletta/why-nats-streaming-server-7f96f0d92b53?source=rss-515ed559018b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f96f0d92b53</guid>
            <category><![CDATA[rabbitmq]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[nat]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Thomas A. Valletta]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 15:39:20 GMT</pubDate>
            <atom:updated>2017-12-19T15:46:16.934Z</atom:updated>
            <content:encoded><![CDATA[<p>Software engineers that want to scale their complex applications often turn to messaging to decouple services. Among the most popular products that are chosen to meet this need are Redis Pub/Sub, RabbitMQ and Kafka. Each have advantages and disadvantages.</p><p>Redis Pub/Sub is the minimalist offering. Subscribers get low latency delivery of messages as they are published. It lacks durability, but provides the basic building blocks and a reliable platform for building to custom needs.</p><p>RabbitMQ also provides a publish/subscribe model, but with a thousand other features including message durability, fan out and guaranteed delivery. RabbitMQ can, however, be difficult to operate at large scale, and can be taken down by misbehaving clients.</p><p>Kafka effectively addresses the issues of scaling and misbehaving clients through a design based on transaction logs. It was designed by LinkedIn to be massively scaleable. Though it is technically publish/subscribe, its consumers are required to poll for new messages and manage their own location in the queue.</p><p>Nats Streaming Server is designed like Kafka to handle enormous scale. Most published benchmarks show Nats Streaming Server outperforming Kafka in both latency and throughput. Because it is newer, it lacks the tooling and ecosystem that Kafka has developed. But the Nats Streaming Server provides many of the developer conveniences that RabbitMQ does by pushing messages out to clients and managing where clients are in the queue.</p><p>So if you are having a difficult time with the trade-offs of choosing between the speed of Redis Pub/Sub, the ease of RabbitMQ and the scale of Kafka, you might check out Nats Streaming Server.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f96f0d92b53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Promises with the MongoDB Node client]]></title>
            <link>https://medium.com/@tvalletta/promises-with-the-mongodb-node-client-d30c4549028d?source=rss-515ed559018b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d30c4549028d</guid>
            <category><![CDATA[promises]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[bluebirdjs]]></category>
            <dc:creator><![CDATA[Thomas A. Valletta]]></dc:creator>
            <pubDate>Wed, 15 Jun 2016 14:51:29 GMT</pubDate>
            <atom:updated>2016-06-15T14:51:29.416Z</atom:updated>
            <content:encoded><![CDATA[<h4>Now with Bluebird.js disposers!</h4><p>The MongoDB node client is more flexible than many people know. It will return a promise if the callback parameter is omitted. For example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ac09f9db9258bc1c2e47fcfb29e4c221/href">https://medium.com/media/ac09f9db9258bc1c2e47fcfb29e4c221/href</a></iframe><p>MongoDB uses <em>es6-promise</em> to implement promises. This allows them to be as spec compliant as is currently possible.</p><p>If you are a fan of <em>Bluebird.js</em> and think that Bluebird style disposers would simplify your MongoDB connections, that can be easily accomplished as well.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/02f3c6231a411091317b2e2399f1c18e/href">https://medium.com/media/02f3c6231a411091317b2e2399f1c18e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d30c4549028d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>