<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Traefik Reverse Proxy Micro Services on Roger Welin</title><link>https://rogerwelin.github.io/categories/traefik-reverse-proxy-micro-services/</link><description>Recent content in Traefik Reverse Proxy Micro Services on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Mon, 17 Sep 2018 19:43:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/traefik-reverse-proxy-micro-services/feed.xml" rel="self" type="application/rss+xml"/><item><title>Traefik tutorial - dynamic routing for microservices</title><link>https://rogerwelin.github.io/2018/09/17/traefik-tutorial-dynamic-routing-for-microservices/</link><pubDate>Mon, 17 Sep 2018 19:43:43 +0000</pubDate><guid>https://rogerwelin.github.io/2018/09/17/traefik-tutorial-dynamic-routing-for-microservices/</guid><description>&lt;p&gt;Traefik is an awesome reverse proxy (and load balancer) with lots of backend supports. So why do we need another reverse proxy? (we already have nginx and haproxy that are stable and performant). Don&amp;rsquo;t get me wrong, nginx and haproxy are awesome, but the problem with them is how to manage configuration. In a microservice world configuration are not stable, services come and go and configuration need to be updated to route traffic something that haproxy and nginx are not designed for. Enter traefik.&lt;/p&gt;</description></item></channel></rss>