<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>redis on Poeticoding</title><link>https://www.poeticoding.com/tag/redis/</link><description>Recent content in redis 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/redis/index.xml" rel="self" type="application/rss+xml"/><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>