– High level overview of the hosting platform

– Splitting up compute resources for enterprise clients

– Motivation for choosing Go for a few of the back-end services

– Feeding data to the web dashboard with MongoDB, ECS, a load balancer and Go

– The Go proxy service was built using the standard library (no 3rd party libraries)

– Differences between the free and paid plans

– Displaying a custom page if your Meteor app happens to be down

– Going over a few services, starting with the Docker image builder

– The Go services are in a mono repo but they can be individually deployed

– The next service is the scheduler which is custom built

– How the web dashboard gets updated from events on the back-end

– The last service we’ll cover is for registering SSL certificates with Let’s Encrypt

– Monitoring is very important and they’re using Datadog, plus being on-call

– Postmark and SendGrid are both used to send emails

– Payments are handled through Recurly

– Loggly is used for logging and a bit of analytics

– Handling a lot of incoming notifications and making sense out of alerts

– Choosing AWS for hosting everything and using ECS over EKS

– It’s hosted across multiple AWS regions (Virginia, Ireland and Sydney)

– The open source side of Meteor is very very important

– How Terraform is being used to manage their infrastructure

– ScaleGrid is used to host their MongoDB instances

– How clients store their secrets

– How deployments are handled from development to production

– All data is backed up on a regular basis with lots of redundancy

– Handling big traffic spikes with little warning

– Best tips? Monitor everything and avoid premature optimization

– Check out Filipe on Twitter, his coding education platform and YouTube channel