Fly.io: The reclaimer of Heroku's magic

(christine.website)

528 points sealeck | 2 comments | 15 May 22 19:56 UTC | HN request time: 0.569s | source

Show context

chanux ◴[16 May 22 05:09 UTC] No.31393824[source]▶

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?

replies(5): >>31393892 #>>31393907 #>>31394367 #>>31394688 #>>31416678 #

1. Wuzado ◴[16 May 22 05:32 UTC] No.31393907[source]▶

>>31393824 #

Perhaps just using an embedded DB would be better in your case? Something like Berkeley DB. Alternatively, just Dockerize it, although I assume it's too much upkeep.

While not as "Redis-y", there are some decent KV-ish managed databases out there:

- Firestore - Cloudflare Workers KV - DynamoDB - Bigtable

replies(1): >>31394384 #

2. bcjordan ◴[16 May 22 07:24 UTC] No.31394384[source]▶

>>31393907 (TP) #

One GCP Firestore tip a lot of folks don't realize for non-client-WebSocket-y workloads you can run Firestore in Datastore mode and it acts much more like DynamoDB. Can turn usage bills from $10s per month to pennies, and IIRC gives you faster response times and higher scaling limits in terms of writes per second

↑