Live data from Hacker News

Reliability: It’s not great

community.fly.io

221–230 of 476 posts

Re: Reliability: It’s not great

#221

Earlier quoted context omitted.

Dokku is also nice and battle-tested: https://dokku.com/ And may I also plug Lunni, a self-hosted Docker Swarm-based PaaS I'm working on right now: https://lunni.dev/ Both work pretty well on $5 servers.

Lunni looks really interesting! Looks like a Coolify competitor, I'll definitely check it out. Do you have a Discord to join? Coolify has one and I found it great to discuss the project and talk directly to the creator. I used to use Dokku but I personally liked the GUI from Coolify so I've been using that. Nice to see that you have a GUI as well, makes configuring apps a lot easier.

That's a nice idea actually, thank you! Just launched one:

https://discord.gg/9EAne8g2Pq

(Bridged to Matrix: https://matrix.to/#/#lunni:matrix.org)

Lunni is actually pretty young in terms of community (just me and a few friends now :-), so just a room in Telegram was sufficient so far, but I think it's a good time to start something more official.

Re: Reliability: It’s not great

#222
Thanks for sharing!

Would it help to replace Corrosion with a simpler "Here's my local known state" blob that is POST'd to blob storage (for example) on a major cloud provider, and have another service read that at intervals? Just to make it really simple.

There will be a better way than that, but my thought is if you can make it simpler (known state is always just pushed, so missing updates auto-recovers and avoids corruption) then you can be building on top of a more stable service discovery system.

Centralized secret storage, can you keep the US instance read/write, but replicate read-only copies (a side-car tool that copies the database to other regions at various intervals?) so each region can fetch secrets locally?

Or perhaps both can be solved with a general "Copy local state to other regions" service that is pretty simple but gives each region its own copy of other region's information (secrets, provisioning states, ...).

I've needed to do similar things for some of the apps I've built, where a service needed another (simpler) service in front of it to bear the traffic load but was operationally simple (deferred the smarts to the system it was using as the source of truth) and automatically recovered from failure due to its simplicity.

Re: Reliability: It’s not great

#223
post #205

Earlier quoted context omitted.

I'm going to plug Coolify, an open source Heroku alternative (with Docker support too) that I'm using on a cheap $5 Hetzner server which is a lot cheaper than the equivalent Fly or Render etc service, and it really doesn't have much upkeep from me even if you add in the time setting up the server initially, which is like an hour, and afterwards, it Just Works™. https://coolify.io

No experience with either, but how does Coolify compare to Dokku, the OSS Heroku alternative I've been hearing about until now?

Dokku doesn't have a GUI which is the main reason I switched from Dokku which I used to use before.

Re: Reliability: It’s not great

#224
> In response, we’ve shipped a project called Corrosion. Corrosion is a gossip > based service discovery system.

I wonder why they didn't try to use Serf[1] for this, since they were so into HashiCorp tools. It also uses the gossip protocol.

1: https://www.serf.io/docs/index.html

Re: Reliability: It’s not great

#225
post #149

Well, I feel for them. Scaling up is a bitch. I've been lucky, in the past, but a lot of that, is because I have "overengineered," and the tools/frameworks have advanced to meet the new demand. I am in the middle of a complete, bottom-to-top rewrite of the app we've been developing for the last couple of years. It's going great, but making this leap was a fraught decision. It's mainly, so I wouldn't have to write a p…

Hope this isn't a dumb question, but what's an "SPM module"?

Sorry. Apple-specific.

Swift Package Manager.

https://littlegreenviper.com/series/spm/

The only dumb question, is the one I don't ask.

Re: Reliability: It’s not great

#226
post #115

Earlier quoted context omitted.

This simply isn't true. At least not for EEC(Norway).

I have never seen a company without Google Search, Google Chrome, AWS, Microsoft 360 and the lot. Which alternatives are they based on?

Those would not contain PII from your users though, unless you have terrible policies about copying personal information in random Google Docs.

Re: Reliability: It’s not great

#227

Earlier quoted context omitted.

Lunni looks really interesting! Looks like a Coolify competitor, I'll definitely check it out. Do you have a Discord to join? Coolify has one and I found it great to discuss the project and talk directly to the creator. I used to use Dokku but I personally liked the GUI from Coolify so I've been using that. Nice to see that you have a GUI as well, makes configuring apps a lot easier.

That's a nice idea actually, thank you! Just launched one: https://discord.gg/9EAne8g2Pq (Bridged to Matrix: https://matrix.to/#/#lunni:matrix.org ) Lunni is actually pretty young in terms of community (just me and a few friends now :-), so just a room in Telegram was sufficient so far, but I think it's a good time to start something more official.

Thanks, just joined. One thing I noticed is that the CI/CD setup for GitHub/lab is still based on the CI files themselves. What I like about Coolify and didn't like about others is that I could simply install a GitHub app to my account and Coolify would automatically pull my repositories and even set up git push to deploy for me, no messing around with CI files needed.

https://lunni.dev/docs/deploy/from-git/#github vs https://docs.coollabs.io/coolify/sources

Re: Reliability: It’s not great

#228

Fundamentally I think some of the problems come down to the difference between what Fly set out to build and what the market currently want. Fly (to my understanding) at its core is about edge compute. That is where they started and what the team are most excited about developing. It's a brilliant idea, they have the skills and expertise. They are going to be successful at it. However, at the same time the market is…

What are the limitations to heroku that people are going to Fly for? Maybe there's a standard article that would be useful to read about it?

This is an old doc from fly so I’m not sure how much of it is still accurate, but it talks about some of the stuff Heroku didn’t have that they have: https://fly.io/docs/app-guides/speed-up-a-heroku-app/

> There's no support for a single dedicated IP address for your application. With Heroku, your application's CPU resources are mostly located in one datacenter. Heroku doesn't support HTTP2 or Brotli compression and it doesn't do Edge TLS termination. And it doesn't run your applications on dedicated MicroVMs. These are all things that Fly's Global Application Platform does.

The other comment that mentions Heroku dropping low cost plans is the reason for the explosion in growth as I understand it though.

Re: Reliability: It’s not great

#229
post #88

Earlier quoted context omitted.

I know I've personally spent a large portion of my time updating systems to be compliant in the last few years, in North American companies.

... Are those North American companies prepared to willingly break EU laws then? Because in my (amateur) understanding it’s logically impossible to satisfy both CLOUD Act requirements and EU data protection ones (not just GDPR, but general due-process rights the CJEU considers required for privacy violations and US courts deny noncitizens).

Yes.

Whenever a US law and a foreign law conflict, the US law always wins when you are in the United States. Complying with US laws is also a perfectly valid defense if a European citizen or state ends up bringing action against you in a US court.

Re: Reliability: It’s not great

#230
post #119

Earlier quoted context omitted.

(Render founder) We're still on public clouds because even if it doesn't help with margins, it helps us move faster on features our customers want. It's all one big prioritization problem (and lots of little ones too!).

I'm curious how significant a risk products like AWS Lightsail are to your business - it seems you are competing in the same market, but: 1. They have vastly different ongoing capital and cashflow requirements than you do. 2. They have all the leverage when it comes to the question of your continued operations on their cloud. I'm also curious if they have already offered to just buy you out since you're clearly succe…

> how significant a risk products like AWS Lightsail are to your business - it seems you are competing in the same market

Not Anurag, but as ex-Stripe himself, he may appreciate AWS Flexible Payment Service vs. Stripe parallels here: https://news.ycombinator.com/item?id=34513430

Post reply on HN