3 ms·
> we assign distinct public IPv4 addresses to each app running on Fly.io. Why not charge a premium for even one distinct public IPv4 address? Most application
by mwcampbell 5y ago
> we assign distinct public IPv4 addresses to each app running on Fly.io.
Why not charge a premium for even one distinct public IPv4 address? Most applications are HTTP(S)-based and could share a reverse proxy with a thousand other apps, right? You could even spin the lack of distinct public IPs as a positive: zero IPv4 footprint.
- tptacek 5y agoThe post talks about this (I take your point that we didn't write about it clearly enough). There are two reasons: 1. We don't want to do anything to discourage people from building non-HTTP applications on Fly.io, because we're fans of weird applications. 2. Just giving every app a routable address simplifies our own deployment logic (at the expense of acquiring blocks of IP addresses). Really, the reason we were moved to write about this is (2); specifically: so long as IPv4 addresses are appreciating assets (as current buyers, we can report: they remain appreciating assets), then there is a sense in which holding IPv4 blocks is really just holding money in a different, somewhat less liquid (but potentially profitable) form. We're not saying that's a good thing, just that it's interesting that you can essentially take out a mortgage on a large block of addresses and live in it while it appreciates.
- kevin_thibedeau 5y agoTLS doesn't require HTTP.
- tptacek 5y agoSure. You take my meaning, I assume. Virtually all of the TLS apps on Fly.io are HTTPS apps.
- mike_d 5y ago> Most applications are HTTP(S)-based and could share a reverse proxy with a thousand other apps, right? Try running your SaaS app on an IP address shared with a porn site and you'll quickly discover all the strange ways older middle-boxes try to police network traffic.