I'm so glad Fly exists. Every other edge focused thing out there I'm aware of are "serverless" which these days basically means they charge per request. That's fine for a lot of use cases, but the unit economics of the per request pricing model means it's really hard to operate a predictably sustainable (i.e. profitable) business without also charging our customers on a usage basis, or enforcing limits on usage, neit…
> Every other edge focused thing out there I'm aware of are "serverless" which these days basically means they charge per request. Workers Unbound is $1 for ~6.6M requests (+ runtime at $0.0000015 per sec / $12.5 for 1M GB-sec). That's super cheap considering free egress, which brings me to... > Fly just gives us compute at the edge for a predictable price per unit of actual compute resources as opposed to requests..…
Free Postgres databases for small projects
191–200 of 231 posts
Re: Free Postgres databases for small projects
#192Other than Heroku, there is no app deployment platform with databases right ? Even vercel doesn't have a database layer. Fly.io again gives VM - not an managed app layer.
> Other than Heroku, there is no app deployment platform with databases right ? Are we not counting the major public clouds as “app deployment platforms” now?
Re: Free Postgres databases for small projects
#193Re: Free Postgres databases for small projects
#194Earlier quoted context omitted.
> Every other edge focused thing out there I'm aware of are "serverless" which these days basically means they charge per request. Workers Unbound is $1 for ~6.6M requests (+ runtime at $0.0000015 per sec / $12.5 for 1M GB-sec). That's super cheap considering free egress, which brings me to... > Fly just gives us compute at the edge for a predictable price per unit of actual compute resources as opposed to requests..…
We don't bill for internal Postgres bandwidth anymore. Bandwidth in general is a good point though. No one _actually_ offers unlimited bandwidth. We haven't figured out how to be transparent about bandwidth costs AND check that box for people yet, though.
Isn't cloudflare's whole shtick about not having egress fees? https://blog.cloudflare.com/workers-now-even-more-unbound/
Re: Free Postgres databases for small projects
#195Though as part of the signup I'm asked for a credit card. So it's not really "free". It's for credit card users only that need to trust they won't charge you.
Re: Free Postgres databases for small projects
#196Earlier quoted context omitted.
For a company that says it makes it super easy to deploy a container image and mentions that all you need to do "Write your code, package it into a Docker image, deploy it to Fly's platform"[0], they sure have a dearth of documentation on how to deploy an existing docker container. I am not sure if I'm missing something or what, but here's where I looked: * googled 'docker fly' and a blog post that references docker…
You know, you're not really missing anything, we just don't connect the dots very well. Install CLI, run `fly launch` in a directory with a Dockerfile, and it should just work. Most of our users don't start with a Docker image though, they start with Phoenix. What you're seeing is a little bit of indecisiveness in how we target the docs.
Does this build the Docker image locally and send it to Fly.io, or does it send the whole build context to Fly.io and build the image remotely?
Re: Free Postgres databases for small projects
#197Earlier quoted context omitted.
This is true, but we aren't going to bill per request. We really can't, since we support arbitrary UDP and TCP services. I don't really want to promise anything we haven't shipped yet. But my perfect cloud service (a) charges me when VMs are alive and (b) gives me the tools I need to create/remove/stop/start/suspend/resume VMs based on either network activity or metrics. One flaw of Fly.io right now is that it's rela…
> charges me when VMs are alive and You still need that capacity, don't you? You will have to adjust the pricing but i doubt it will cost either of us any less, whether you allocate it.
The nice thing about spreading hardware around the world is that we have excess capacity wherever it's dark. If you're doing latency insensitive work like batch jobs, we can schedule it somewhere that would otherwise be idle.
Aggregate capacity is smaller than the sum of the individual apps capacity requirements. So we both benefit.
Re: Free Postgres databases for small projects
#198Though as part of the signup I'm asked for a credit card. So it's not really "free". It's for credit card users only that need to trust they won't charge you.
Re: Free Postgres databases for small projects
#199Re: Free Postgres databases for small projects
#200Earlier quoted context omitted.
You know, you're not really missing anything, we just don't connect the dots very well. Install CLI, run `fly launch` in a directory with a Dockerfile, and it should just work. Most of our users don't start with a Docker image though, they start with Phoenix. What you're seeing is a little bit of indecisiveness in how we target the docs.
> Install CLI, run `fly launch` in a directory with a Dockerfile, and it should just work. Does this build the Docker image locally and send it to Fly.io, or does it send the whole build context to Fly.io and build the image remotely?
You can control this with "fly deploy --remote-only" and "fly deploy --local-only". Don't use both, it might cause a paradox.