Spinning up a cluster of docker services per customer

[ignoramous]

@mvanlonden

Will machines across apps be able to communicate using *.internal domains?

Yes, but apparently one can carve out network namespace for a group of apps (in the same org) to isolate them away: Multi tenant applications - #23 by thomas

@mvanlonden

Create an app per service and then spin up customer instances of that service as machines nested under their respective apps.

Yep, you can deploy different images (Machines) under a single Fly Machine app with its own env, build / release_commands, services… if you’d continue to use the GraphQL APIs, then I don’t see why not. Except… public IP addresses (this might be a big deal) and secrets (and may be a few other things that I can’t recall off the cuff) are common to all Machines of an app, which might be deal breaker.

These previous discussions may be of interest:

1. Machines not responding to Non Standard Ports - #8 by dfragnito
2. Machine Metrics Query and App Usage Report - #4 by kurt
3. Machines + builder + private docker registry?
4. Multi-region application where users / sessions are pinned to one region? - #3 by ignoramous