You've made it to the end!

I hope you had a good time learning with me how to deploy to the edge with Fly.io.

Deploying long-running servers and having your data as close to your users as possible... It just blows my mind what we have available to us!

We have availability and data consistency with transactional consistency, giving us the best of all worlds.

Thanks for learning with me, and I look forward to hearing about the cool things you running on the edge!

Presenter: [0:01] I hope you had a good time learning with me how to deploy to the Edge with Fly.io deploying long-running servers and your data as close to your users as possible. It blows my mind what we have available to us and getting the best of all worlds.  
  
[0:16] We have availability. We have data consistency with the transactional consistency stuff that we did. It's really cool what we've been able to do. I look forward to hearing about the cool things that you're running on the Edge. I'm so happy that you're with me.

Concluding the Deployment Tutorial

The closer you are to the server, the faster your experience will be.

It wasn't long ago that web app developers had to choose a region where they thought the bulk of their users would be located, leaving people on the other side of the world with longer waiting times.

Fortunately, times have changed and it's now possible to deploy an application and have it be distributed worldwide– and it's not as tough as it sounds!

This tutorial will show you how to deploy a multi-region Node.js application with a persistent database, ensuring optimal performance no matter where your users are located thanks to Fly.io.

Here are some of the topics you'll tackle along the way:

## Deployment with Fly.io

The first step is to get acquainted with configuring Docker and Fly's CLI tool by deploying the demo Counter app.

After all, you have to have everything working in one region before you make it work in multiple regions!

## Data Persistence and Health Checks

You'll learn how to create persisted volumes to avoid data loss, as well as the steps for setting up health checks and custom endpoints for monitoring the app.

## Automatic Deployment with GitHub Actions

The deployment process is pretty easy thanks to Fly's CLI tool– but automating it makes it even easier 😎

## Creating a Staging Environment

Testing your app safely in a staging environment before it goes live is a great way to ensure a smoother rollout with reduced risk of downtime. This is a huge benefit that comes from a minimal amount of configuration.

## Embrace the Distributed Architecture

Once you understand how the pieces fit together, you'll be ready to deploy the demo application to regions all around the world.  
But it's not just the app itself. Fly.io supports LiteFS, which is used to replicate SQLite databases. This means your database can live on the edge, right beside your application.

Everything you learn about deployment in this tutorial is ready for you to put into action for your own applications.

Ready to fly?

Let's do this!

Kent C. Dodds

Learn how to deploy a Node.js application that persists data to multiple regions.

Intro to Deploy Distributed Apps with Node.js & Fly

Fly.io is the service we'll use for deploying our app. The first step is signing up for an account. 

Signing Up for Fly.io

We will deploy to Fly with Docker. A Dockerfile is used to tell Docker the steps to take to run our app.

Setting Up Docker

With the Dockerfile ready to go, let's deploy our app to Fly.

Deploying to Fly with Docker

Fly.io

Project Setup and First Deployment

Currently the counter state is reset to zero after every deployment. Creating a persistent volume with Fly solves this problem.

Persist Application Data Between Deployments

While not a replacement for testing, Fly offers health checks to prevent broken code from being deployed.

Adding Deployment Health Checks

Fly allows you to SSH into your app's virtual machine and run commands. Updating the Dockerfile to create a shortcut script makes the process run more smoothly.

Add a SQLite Console Shortcut with the Dockerfile

Configure GitHub Actions for Automatic Deployment

A staging environment is useful for play testing before pushing changes to production. This can be quickly set up with GitHub Actions and Fly

Add a Staging Environment

Persisting Data and Automatic Deployment

Deploying sites to multiple regions is less of a challenge than handling data. Fortunately Fly makes it easy to prepare for multi-region data.

Prepare for Multi-Region Data with LiteFS

If you're migrating to LiteFS from an existing application, you may have data you'd like to keep. Luckily, there's an easy process for importing it into LiteFS.

Import Existing Data into LiteFS

The Consul lease type provides a resilient solution in case the primary instance of our application goes down.

Set Up the Consul Lease Type

In order to make sure only our primary region attempts to write data, we'll set up a proxy server configuration for LiteFS

Set Up a Proxy Server for Multi-Region Database Support

With all the setup in place, it's time to scale our deployment to multiple regions, and test to confirm it's working as expected.

Deploy Web Applications All Over the World

Deploy Web Applications All Over the World

Transcript

Concluding the Deployment Tutorial

Transcript