4 ms·

Could someone elaborate on the right "use cases"? Just curious about other's people definition, as I imagined Fly.io as a more self-served BaaS (mostly for web

• janee 4y ago
  My guess would be something like: - startups, small teams, no devops. - horizontally scalable monoliths. - no complex infra needs. Haven't used fly.io but strongly considering migrating over from Heroku and above is roughly what I would say is a good fit for Heroku so hopefully it's the same on fly.io
  • jtokoph 4y ago
    I haven’t done it myself yet (soon), but they seem great for even multi service apps. All apps in an org are automatically connected to each other via a wireguard network. Internal communication and service discovery is provided by special internal dns resolution. It feels like the simplicity of Heroku deployments with the power and security of an AWS VPC.
• kasey_junk 4y ago
  The big win is web applications that are read heavy and have geographically dispersed users.