<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Route53 - Tag - Filipe Felisbino</title><link>https://felisbino.dev/tags/route53/</link><description>Route53 - Tag - Filipe Felisbino</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 10 Sep 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://felisbino.dev/tags/route53/" rel="self" type="application/rss+xml"/><item><title>Docker: Service discovery for docker containers on AWS</title><link>https://felisbino.dev/posts/docker-service-discovery-on-aws/</link><pubDate>Sat, 10 Sep 2016 00:00:00 +0000</pubDate><author>Filipe Felisbino</author><guid>https://felisbino.dev/posts/docker-service-discovery-on-aws/</guid><description>&lt;p>These days we see lots of fancy ways to do service discovery with docker. You see examples of people using
etcd, zookeeper, consul and so on. I recently had a project to migrate some solr clusters to docker and I
started looking at some of those tools and how they would fit that our current infrastructure.&lt;/p>
&lt;p>After some researching I found that the KISS way of doing service discovery on our environment was to use route53.
The main reasons for this decision were:&lt;/p></description></item></channel></rss>