How MediaMachine uses Traefik for easy-to-maintain request routing
MediaMachine.io is an IaaS platform for user-generated video content and we use as the reverse proxy in our network layer. This blog details how we leverage Traefik to run a highly-available infrastructure that is also easy for us to maintain.
Traefik is a popular, open-source reverse proxy implementation in Go. It is actively maintained by Traefik Labs (they used to be called Containous). Traefik allows you to expose network resources to the internet (or even other networks), manage routing based on hostnames, url paths etc.
You can use Trae fik to redirect HTTP traffic to another, private IP address, to provide HTTPS access for your customers or to provide a reverse proxy to web servers sitting in your internal VPC. This is especially useful if you run you infrastructure on a public cloud, such as AWS.
As the name suggests, the most obvious thing we want from a reverse-proxy is to proxy our servers sitting inside our private VPC to the outside world. However, we want to do it in a way that is easy to configure and highly dynamic. We elastically scale our servers based on load and we can’t have a static mapping of external <-> internal server IP pools.
