3 ms·
We switched from Fly to CF workers a while ago, and never looked back
by DataOverload 2y ago
We switched from Fly to CF workers a while ago, and never looked back
- eek2121 2y agocongrats on not developing a playbook for the time you have to 'look back'. Providers will fail. good contingencies won't. ...hears faint sound...I SAID GOOD, QUIET YOU!
- punkpeye 2y agoThey are fundamentally different. If Cloudflare provided a way to host docker containers with volumes though, that would be game over for so many paas platforms.
- stoicjumbotron 2y agoCan't wait: https://blog.cloudflare.com/container-platform-preview/ https://blog.cloudflare.com/container-platform-preview/
- rstupek 2y agoHow are they equivalent?
- frakkingcylons 2y agoI switched from apples to oranges and never looked back.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- pier25 2y agoOur stuff on CF Workers has been working non stop for years now. About 6 months ago we migrated our most critical stuff from Fly to CF and boy every time Fly has issues I'm so glad we did.
- jpgvm 2y agoToo much custom stuff too quickly, there is a lot of efficiency in vertical integration and a fully cohesive stack but it takes a very long time to stabilize if you take that route. We spent months trying to convince them of problems with their H2 implementation in their LB/proxy (they insisted nginx was at fault, spoiler - it wasn't) but had to leave (we also went to CF, which has its own problems). Eventually one of their employees wrong a long blog post about H2 that made it obvious they finally found and fixed those problems but months too late for my employer at the time. It would have been infinitely better for us if they could have just fixed their stability problems, that abstraction suited us as did their LB/proxy impl and SNI pricing. I wish them well, some really smart folk over there but I can imagine these reliability problems are probably really grinding down morale.