My thoughts about Fly.io (so far) and other newish technology I'm getting into
blog.hartleybrody.com
My thoughts about Fly.io (so far) and other newish technology I'm getting into
1–10 of 111 posts
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#2Cloud Run is an alternative to fly.io that scales to zero so it can be much cheaper but with added cold starts.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#3An unrelated, yet honest question.
There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#4An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
For better or worse, fly.io has as a principal tptacek, who's at the top of the HN leaderboard and so has built up a lot of goodwill here.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#5An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
Given that Fly.io has been part of YC W20, and that they make some interesting technology choices (eg all-in on sqlite), it creates more traction on this site.
Typically this type of thing goes in phases, and I wouldn’t worry about it, assuming you’re already OK with HN being biased towards YC-funded startups.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#6An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
As per dang's comment a few days back(1)
> I wish more startups would achieve this, YC or not. Whenever I run across one that's trying to succeed on HN, I try to help them do so (YC or not)—why? because it makes HN better if the community finds things it loves here. Among the startups of today, I can think of only two offhand who are showing signs of maybe reaching darling status—fly.io (YC), and Tailscale (not YC).
Personally too both these companies are doing a lot of incredible things. I also love Litestream, phoenixframework and other things they are doing.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#7An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
The last time I remember such a run on HN was when we created Docker. It was on the front page or mentioned in front page comments almost daily for at least 6 months (late 2013 early 2014)
Fly.io has a great combination of user virality/momentum and fundamentally technically interesting content on a wide range of topics.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#8An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
Generally, it is all YC hype. HN is biased towards YC startups.
There are other alternatives like Render.com, railway.app, etc but it is clear that fly.io is unsurprisingly overhyped by the HN crowd, especially if you are looking for a Heroku alternative.
It’s like asking a barber if you need a haircut.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#9A little note about read replicas and problems I've discovered. It's often the case in code that you write a value to the DB then immediately read it back often in the form of a different query somewhere else.
If you are setup to do some kind of a round robin read from the read replicas you can often get a different read from what you wrote as the value hasn't replicated to your read replicas yet. The solution is to use the write endpoint when reading after a write.
He says that here but just wanted to point out that it can happen inside an api and cause real issues with data.
Re: My thoughts about Fly.io (so far) and other newish technology I'm getting into
#10An unrelated, yet honest question. There have been many posts hitting the HN frontpage regarding fly.io recently. Is it healthy to have so much content about a single PAAS platform showing up here so often now?
Fair question. I’d rather see more of this than culture-war and politics.