While MediaMachine is a new product, we’ve been writing http-based apis ( usually RESTish, with json ), for a looooooooooooong time and thought it would be worthwhile to talk through and explain some of our most basic production metrics. Hopefully this can help others who are new to API monitoring and want to get better visibility into what’s happening.
MediaMachine.io is an IaaS platform for user-generated video content and we use Traefik as the reverse proxy in our network layer.
In a previous post, we talked about how Traefik fits into our infrastructure and helps us serve requests with ease. This runbook is an extension to that - an overview of things we found important to highlight for someone looking to know more about running Traefik themselves including useful configuration snippets.
Here is our runbook for getting setup with Traefik in your environment:
MediaMachine.io is an IaaS platform for user-generated video content and we use Traefik 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 Traefik 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.
Let’s see how Traefik fits into a modern network plane.
