3 ms·
One of our engineering teams wanted to use fly.io instead of kubernetes that I was running in AWS for the company. They really liked its ease of use and they re
by djha-skin 3y ago
One of our engineering teams wanted to use fly.io instead of kubernetes that I was running in AWS for the company. They really liked its ease of use and they really wanted to use it. Unfortunately fly.io only allowed 5,000 concurrent TCP connections, and there's was a chat app that needed to maintain many more web sockets than that for each instance that was running (More like 50,000).
So they ended up switching to kubernetes and AWS.
Fly.io is nice, but as far as scale is concerned, it's entry level.
- garganzol 3y agoThe TCP connection limits are in place only when a central HTTP/HTTPS routing/termination is used. But you can turn that off by a config parameter in fly.toml file and by allocating static IPv4/IPv6 addresses for your app. By doing so, your app will be then fully responsible for handling all HTTP/HTTPS traffic by itself without external caps.
- miroljub 3y agoIt's funny how people spend a lot of time and, in the end, choose a worse (unfavourable?) product just because of their inability to find a config switch that would solve all their issues and enable them to use their tool of choice.
- scetron 3y agoThere's quite a few reasons why it happens though. Perhaps the feature was available, perhaps there was no documentation or poor documentation. Perhaps this is more complex in some way? We don't really know.
- ctvo 3y agoThere's a another reason to avoid fly.io outside of platform capabilities: their outages caused by growing pains. If it were me, I'd circle back in a year or two.