←back to thread

Fly.io: The reclaimer of Heroku's magic

(christine.website)
528 points sealeck | 8 comments | 15 May 22 19:56 UTC | HN request time: 0.478s | source | bottom
1. normie3000 ◴[15 May 22 20:28 UTC] No.31390785[source]▶
How mature is fly.io?
replies(2): >>31391027 #>>31391155 #
2. throwawaycuriou ◴[15 May 22 20:55 UTC] No.31391027[source]▶
Define mature
3. mrkurt ◴[15 May 22 21:09 UTC] No.31391155[source]▶
We are DigitalOcean circa 2015 mature. Good enough for some very large customers, good enough for many developers, not some place I'd run pacemaker infrastructure.
replies(2): >>31391261 #>>31391296 #
4. indigodaddy ◴[15 May 22 21:21 UTC] No.31391261[source]▶
Does anyone run pacemaker on non-baremetal? Can you even? I’m aware you’re just using it as an analogy/example, but was just wondering..
replies(2): >>31391950 #>>31401784 #
5. sanjayio ◴[15 May 22 21:24 UTC] No.31391296[source]▶
Where would you feel comfortable running pacemaker infra? Half-joking here.
replies(1): >>31391912 #
6. ◴[15 May 22 22:47 UTC] No.31391912{3}[source]▶
7. antod ◴[15 May 22 22:53 UTC] No.31391950{3}[source]▶
I did run some VRRP or CARP stuff (forget the specific tool/protocol - but that's kinda like pacemaker right?) in an immature OpenStack cloud once that didn't have a good LBaaS yet. It was a semi supported hack documented by the provider.
8. ecnahc515 ◴[16 May 22 18:55 UTC] No.31401784{3}[source]▶
FWIW, I'm pretty sure OP was referring to literal pacemakers, as in, the things that keep people's hearts beating.