You can now use
<groupname>.process.<appname>.internalas a hostname, and our internal DNS will resolve it to specific process groups of an app.
One thing they haven’t been particularly great at, though, is communication. They can talk to the app as a whole, but there was no way to filter out specific process groups to talk to. In particular, we’ve seen many cases recently where people have apps with a frontend component, a backend component, and a requirement to update them together - usually we’d suggest keeping these as separate apps, but if they have to update together, that’s not a good fit.
Now, you can deploy an app with a
backend process group, and the
frontend process can communicate with the backend process via
Let’s take a look at this in action.
I have a simple
app = "ali-process-dns-example" primary_region = "atl" [processes] a = "sleep inf" b = "sleep inf" [build] image = "ubuntu"
fly launch --now --ha=false, I should have one “a” and one “b” machine.
❯ fly m list 2 machines have been retrieved from app ali-process-dns-example. View them in the UI here ali-process-dns-example ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE 148edd40fed989 delicate-dawn-5150 started atl library/ubuntu:latest fdaa:1:a82a:a7b:e6:3aa1:9d6b:2 2023-05-23T19:52:13Z 2023-05-23T19:52:14Z v2 a shared-cpu-1x:256MB e2865502c4d286 withered-pond-973 started atl library/ubuntu:latest fdaa:1:a82a:a7b:e5:ff66:ea2:2 2023-05-23T19:52:26Z 2023-05-23T19:52:26Z v2 b shared-cpu-1x:256MB
I’ll hop into one of them, let’s go with the “a” machine, and install
dig, a tool for performing manual DNS lookups.
❯ fly console --machine 148edd40fed989 Connecting to fdaa:1:a82a:a7b:e6:3aa1:9d6b:2... complete root@148edd40fed989:/# apt update && apt install -y dnsutils
Now, I should be able to look up “b”'s IP.
root@148edd40fed989:/# dig +short AAAA b.process.ali-process-dns-example.internal fdaa:1:a82a:a7b:e5:ff66:ea2:2
Lo and behold, it’s the same IP that
fly m list gave us!
Of course, you don’t have to use
dig to do this. It’s just a hostname, and our DNS is the part doing the magic
In the real world, you probably won’t be spinning up machines to run
dig (not judging if that’s your hobby), but this is a nice building block for connecting pieces of a larger application together!