<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pubsub on Poeticoding</title><link>https://www.poeticoding.com/tag/pubsub/</link><description>Recent content in pubsub on Poeticoding</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 04 May 2019 19:16:14 +0000</lastBuildDate><atom:link href="https://www.poeticoding.com/tag/pubsub/index.xml" rel="self" type="application/rss+xml"/><item><title>Distributed Phoenix Chat with PubSub PG2 adapter</title><link>https://www.poeticoding.com/distributed-phoenix-chat-with-pubsub-pg2-adapter/</link><pubDate>Wed, 30 Jan 2019 16:44:08 +0000</pubDate><guid>https://www.poeticoding.com/distributed-phoenix-chat-with-pubsub-pg2-adapter/</guid><description>&lt;p>In this article we&amp;rsquo;ll see how to cluster the Phoenix Chat nodes, using a really powerful functionality embedded in BEAM (the Elixir/Erlang VM), for easily communicate between Elixir nodes. We&amp;rsquo;ll then see how &lt;code>pg2&lt;/code> works and inspect how Phoenix efficiently broadcasts the messages in a distributed chat app.&lt;/p></description></item><item><title>Distributed Phoenix Chat using Redis PubSub</title><link>https://www.poeticoding.com/distributed-phoenix-chat-using-redis-pubsub/</link><pubDate>Wed, 23 Jan 2019 18:21:34 +0000</pubDate><guid>https://www.poeticoding.com/distributed-phoenix-chat-using-redis-pubsub/</guid><description>&lt;p>In the previous article, &lt;a href="https://www.poeticoding.com/create-a-high-availability-kubernetes-cluster-on-aws-with-kops/">Create a High-Availability Kubernetes Cluster on AWS with Kops&lt;/a>, we have seen how to create a Kubernetes cluster and how to deploy the Phoenix Chat app. The single node configuration worked well, but when we tried to scale out we saw that the messages were not sent to all the browsers.&lt;/p></description></item></channel></rss>