– What it was like using Elixir back in 2017

– Elixir handles 500k requests a day and motivation to use Elixir / Phoenix

– The process to upgrade the code base to use Phoenix contexts

– Oban is being used to handle background jobs

– Sending out notifications and webhooks with custom code

– Using Mix format as part of a CI pipeline with GitHub Actions

– Breaking out the mail service into its own service

– About 28k lines of Elixir and 2k lines of JS

– Server rendered app with EEx vs going the SPA / API route vs Live View

– Supplying a status page embed widget for customers and custom domains

– Using nginx as a reverse proxy, ETS for caching along with Cloudflare

– Hugo is being used to serve the static marketing site

– Docker is being used in staging and production

– The mailer is hosted on Heroku, everything else is on DigitalOcean

– The hardware specs of the 4-5 DigitalOcean servers and what they do

– They’re running Ubuntu 20.04 LTS and upgraded the servers on the fly

– The servers are manually provisioned and run Docker Compose

– Deploying a feature from development to production

– User logos get uploaded and saved to disk with a Docker volume

– Using BackupPC for backing up the database, certificates and file uploads

– DigitalOcean’s monitoring and Pingdom are being used for various health checks

– Honeybadger and Papertrail for errors + logging, and the Elixir experience

– Best tips? Pick a technology you’re comfortable with and start building

– What it was like hiring Elixir contract workers

– Check out https://statuspal.io/ with promo code PRODUCTION to save 10%