Fly.io: The reclaimer of Heroku's magic

I could relate to the comment on Redis.

  The only things I can see missing are automated Redis hosting by the platform.

There have been so many times I wanted some simple key value store which I do not have to bother about setting up and taking care of. Something like "ambient Redis". It's OK not to have crazy scaling promises. You just enable an API (maybe for a small fee) and just use it.

If and when you get big enough you switch to a setup you bother about setting up and taking care of.

Am I making sense to anyone?

Fly did have a built-in redis cache (albeit multi-tenant / shared) and for the life of me I can't figure out why they'd deprecate it (though, it still works): https://community.fly.io/t/debugging-a-failing-image-without... and https://community.fly.io/t/please-bring-redis-back/1563

If anything, I'd prefer they moved their PaaS more towards serverless and managed offerings than towards IaaS.

On their forums they say they envision some other company handling Postgres too. Personally I would prefer they handle the databases, redis etc because that way the services you need can be provisioned right alongside your app servers otherwise it undermines the value of having edge servers near your users. Heroku could get away with 3rd parties being responsible for the database software because using AWS it was easy for other companies to be in the same region or zone.

https://community.fly.io/t/can-we-get-an-update-on-managed-d...