4 ms·
I'm a bit concerned that the free trial mentions "compute up to 1 vCPU / 256 MB" Why would I need to worry about this for a serverless database provider?
by TobyTheDog123 4y ago
I'm a bit concerned that the free trial mentions "compute up to 1 vCPU / 256 MB"
Why would I need to worry about this for a serverless database provider?
- nikita 4y agoWe are limiting the amount of compute we are giving for free during the technical preview. We will open it up to much large computes later. Like those will be in the paid tier.
- TobyTheDog123 4y agoThat sounds good, but my question was (and I probably phrased it poorly), as a solo developer, why would I need to concern myself with resources associated with servers (compute, CPUs, MBs of RAM) on a serverless platform? I could maybe see it in the sense if it's only applicable when Postgres is executing complex custom queries or whatever, but for any operation? That's a huge red flag, for me at least. When I think of serverless, I think of things like Cloudflare Workers, FaunaDB, Ably.io, all of which have pricing based on the usage of their features, not the consumption of their resources. The whole point being that I can way more easily calculate how many messages my users are sending, than how much CPU all those messages are taking to send. Maybe I'm operating on the wrong definition of serverless, and all of the other features look amazing, but that concept is really a dealbreaker.