←back to thread

Fly.io: The reclaimer of Heroku's magic

(christine.website)
528 points sealeck | 1 comments | 15 May 22 19:56 UTC | HN request time: 0.211s | source
Show context
manigandham ◴[16 May 22 08:08 UTC] No.31394584[source]▶
Fly has a nice DX but unfortunately the platform still has major issues with reliability and networking. There are often problems with deploys leading to stuck and unreachable instances or other networking issues. It's probably exacerbated by the new user growth but the slick deploy workflow can't override having an app that works.

Render and others are interesting but K8S is still fundamentally better considering all the DX progress there making it pretty easy to get a container running in a cluster.

replies(1): >>31394750 #
nik736 ◴[16 May 22 08:43 UTC] No.31394750[source]▶
What exactly makes K8s better?
replies(2): >>31394940 #>>31395210 #
1. sascha_sl ◴[16 May 22 09:19 UTC] No.31394940[source]▶
Definitely not the developer experience.

But as it is often mentioend, as companies and apps grow, so do their requirements and the need for flexibility. I can't think of a more flexible deployment target that handles a lot of the PaaS concerns than Kubernetes, warts and all.

Fly is surprisingly great, volumes + containers is very close to universal for a PaaS, but it certainly can't cover everything that is running in my workplace's kubernetes.