<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ØMQ - The Guide</title>
    <link>https://deploy-preview-950--zguide.netlify.app/docs/</link>
    <description>Recent content on ØMQ - The Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    
	<atom:link href="https://deploy-preview-950--zguide.netlify.app/docs/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>1. Basics</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter1/</guid>
      <description>Chapter 1 - Basics #  Fixing the World #  How to explain ZeroMQ? Some of us start by saying all the wonderful things it does. It&amp;rsquo;s sockets on steroids. It&amp;rsquo;s like mailboxes with routing. It&amp;rsquo;s fast! Others try to share their moment of enlightenment, that zap-pow-kaboom satori paradigm-shift moment when it all became obvious. Things just become simpler. Complexity goes away. It opens the mind. Others try to explain by comparison.</description>
    </item>
    
    <item>
      <title>2. Sockets and Patterns</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter2/</guid>
      <description>Chapter 2 - Sockets and Patterns #  In Chapter 1 - Basics we took ZeroMQ for a drive, with some basic examples of the main ZeroMQ patterns: request-reply, pub-sub, and pipeline. In this chapter, we&amp;rsquo;re going to get our hands dirty and start to learn how to use these tools in real programs.
We&amp;rsquo;ll cover:
 How to create and work with ZeroMQ sockets. How to send and receive messages on sockets.</description>
    </item>
    
    <item>
      <title>3. Advanced Request-Reply Patterns</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter3/</guid>
      <description>Chapter 3 - Advanced Request-Reply Patterns #  In Chapter 2 - Sockets and Patterns we worked through the basics of using ZeroMQ by developing a series of small applications, each time exploring new aspects of ZeroMQ. We&amp;rsquo;ll continue this approach in this chapter as we explore advanced patterns built on top of ZeroMQ&amp;rsquo;s core request-reply pattern.
We&amp;rsquo;ll cover:
 How the request-reply mechanisms work How to combine REQ, REP, DEALER, and ROUTER sockets How ROUTER sockets work, in detail The load balancing pattern Building a simple load balancing message broker Designing a high-level API for ZeroMQ Building an asynchronous request-reply server A detailed inter-broker routing example  The Request-Reply Mechanisms #  We already looked briefly at multipart messages.</description>
    </item>
    
    <item>
      <title>4. Reliable Request-Reply Patterns</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter4/</guid>
      <description>Chapter 4 - Reliable Request-Reply Patterns #   Chapter 3 - Advanced Request-Reply Patterns covered advanced uses of ZeroMQ&amp;rsquo;s request-reply pattern with working examples. This chapter looks at the general question of reliability and builds a set of reliable messaging patterns on top of ZeroMQ&amp;rsquo;s core request-reply pattern.
In this chapter, we focus heavily on user-space request-reply patterns, reusable models that help you design your own ZeroMQ architectures:
 The Lazy Pirate pattern: reliable request-reply from the client side The Simple Pirate pattern: reliable request-reply using load balancing The Paranoid Pirate pattern: reliable request-reply with heartbeating The Majordomo pattern: service-oriented reliable queuing The Titanic pattern: disk-based/disconnected reliable queuing The Binary Star pattern: primary-backup server failover The Freelance pattern: brokerless reliable request-reply  What is &amp;ldquo;Reliability&amp;rdquo;?</description>
    </item>
    
    <item>
      <title>5. Advanced Pub-Sub Patterns</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter5/</guid>
      <description>Chapter 5 - Advanced Pub-Sub Patterns #  In Chapter 3 - Advanced Request-Reply Patterns and Chapter 4 - Reliable Request-Reply Patterns we looked at advanced use of ZeroMQ&amp;rsquo;s request-reply pattern. If you managed to digest all that, congratulations. In this chapter we&amp;rsquo;ll focus on publish-subscribe and extend ZeroMQ&amp;rsquo;s core pub-sub pattern with higher-level patterns for performance, reliability, state distribution, and monitoring.
We&amp;rsquo;ll cover:
 When to use publish-subscribe How to handle too-slow subscribers (the Suicidal Snail pattern) How to design high-speed subscribers (the Black Box pattern) How to monitor a pub-sub network (the Espresso pattern) How to build a shared key-value store (the Clone pattern) How to use reactors to simplify complex servers How to use the Binary Star pattern to add failover to a server  Pros and Cons of Pub-Sub #  ZeroMQ&amp;rsquo;s low-level patterns have their different characters.</description>
    </item>
    
    <item>
      <title>6. The ZeroMQ Community</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter6/</guid>
      <description>Chapter 6 - The ZeroMQ Community #  People sometimes ask me what&amp;rsquo;s so special about ZeroMQ. My standard answer is that ZeroMQ is arguably the best answer we have to the vexing question of &amp;ldquo;How do we make the distributed software that the 21st century demands?&amp;rdquo; But more than that, ZeroMQ is special because of its community. This is ultimately what separates the wolves from the sheep.
There are three main open source patterns.</description>
    </item>
    
    <item>
      <title>7. Advanced Architecture using ZeroMQ</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter7/</guid>
      <description>Chapter 7 - Advanced Architecture using ZeroMQ #  One of the effects of using ZeroMQ at large scale is that because we can build distributed architectures so much faster than before, the limitations of our software engineering processes become more visible. Mistakes in slow motion are often harder to see (or rather, easier to rationalize away).
My experience when teaching ZeroMQ to groups of engineers is that it&amp;rsquo;s rarely sufficient to just explain how ZeroMQ works and then just expect them to start building successful products.</description>
    </item>
    
    <item>
      <title>8. A Framework for Distributed Computing</title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/chapter8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/chapter8/</guid>
      <description>Chapter 8 - A Framework for Distributed Computing #  We&amp;rsquo;ve gone though a journey of understanding ZeroMQ in its many aspects. By now you may have started to build your own products using the techniques I explained, as well as others you&amp;rsquo;ve figured out yourself. You will start to face questions about how to make these products work in the real world.
But what is that &amp;ldquo;real world&amp;rdquo;? I&amp;rsquo;ll argue that it is becoming a world of ever increasing numbers of moving pieces.</description>
    </item>
    
    <item>
      <title></title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/postface/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/postface/</guid>
      <description>Postface #  Tales from Out There #  I asked some of the contributors to this book to tell us what they were doing with ZeroMQ. Here are their stories.
Rob Gagnon&amp;rsquo;s Story #  &amp;ldquo;We use ZeroMQ to assist in aggregating thousands of events occurring every minute across our global network of telecommunications servers so that we can accurately report and monitor for situations that require our attention. ZeroMQ made the development of the system not only easier, but faster to develop and more robust and fault-tolerant than we had originally planned in our original design.</description>
    </item>
    
    <item>
      <title></title>
      <link>https://deploy-preview-950--zguide.netlify.app/docs/preface/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://deploy-preview-950--zguide.netlify.app/docs/preface/</guid>
      <description>By Pieter Hintjens, CEO of iMatix
Please use the issue tracker for all comments and errata. This version covers the latest stable release of ZeroMQ (3.2). If you are using older versions of ZeroMQ then some of the examples and explanations won&amp;rsquo;t be accurate.
The Guide is originally in C, but also in PHP, Java, Python, Lua, and Haxe. We&amp;rsquo;ve also translated most of the examples into C++, C#, CL, Delphi, Erlang, F#, Felix, Haskell, Julia, Objective-C, Ruby, Ada, Basic, Clojure, Go, Haxe, Node.</description>
    </item>
    
  </channel>
</rss>