$49/month for 60k queries… The pricing of these serverless offerings is always completely out of this world.<p>My $5 VPS can handle more queries in an hour. Like, I realize there’s more included, but…<p>Is it truly impossible to serve this stuff somewhere closer to cost? If this is close to cost, is this truly as efficient as it gets?
I was a big promoter of Prisma but can no longer recommend it. They built something really cool but have basically abandoned it, with major issues languishing for years without attention.<p>I guess they were busy working on this instead... for now.
It's not every day you get to launch a hosted Postgres service that has something fundamentally new to offer. That's what we have done with Prisma Postgres, and I'm incredibly excited for it.<p>We are using Firecracker and unikernals to deliver true scale-to-zero without cold-starts. Happy to go into more detail if anyone is interested.
Maybe they can take this opportunity to close the feature gap with other ORM: no support for partial index, no support for partition, bad support of JSON column, no support "for update", no support for "now()", poor query performance.
How does it handles backups, read replicas, failover? And more importantly - how it scales with load? For example our workload fluctuates between 1 vCPU to 128 vCPU in an hour. How it would handle this?
Last time I checked, Firecracker didn't have a very compelling I/O story, which made it in my opinion not completely adequate for running Postgres (or any other database).<p>In contrast, other similar VMM seem to have a better one, like Cloud Hypervisor [1]. Why then FC and not CH? (I've nothing against FC, actually love it and have been using it, but it appears not being the best I/O wise).<p>[1]: <a href="https://github.com/cloud-hypervisor/cloud-hypervisor">https://github.com/cloud-hypervisor/cloud-hypervisor</a>
Let's hope it is not another "Netlify" honeypot aka "settle in boys, generous free plan, port everything and lock yourself in. I'll start adjusting those prices next year when it will cost you $10 even to send some emails from your contact form".
I recall Prism as a player in the GraphQL server field, this was about 8 years ago.<p>Anyone knows what happened to that? According to their website they now offer only Postgres services?
If I already have a postgres operator setup on Kubernetes - what additional benefits is this getting me?<p>Right now super fast start times aren't really needed since it's a database that I expect to be running for a while - ms vs 30s is fine. It's easier to setup a test database on the same machine I'm running automated tests so that may not be a good usecase either.<p>I'm glad that they've made improvements to startup speed and size of the containers which would be good if it's open sourced, but I don't know if this is good as a paid service if you already have an easy way of setting up new clusters in k8s.
Prisma is an absolute joke. I remember hearing so much about it with the hype train, and I looked into it, and it's an absolute catastrophe with a very beautiful homepage. There are GitHub issues where the creator is arguing with people about not supporting foreign key constraints or something, and he didnt understand the use case (cant remember specifics right now, but this is where I immediately noped right out)
I don’t understand the free pricing tier:<p>$18 /million queries, 60k included<p>60k queries are free and then the 60_001st starts incurring costs at 18/1_000_000 per query?
Is there a way to import data in from a table, or would I have to manually break it up into 1kb chunk insert queries?<p>Let's say I have a ~150GB postgres DB right now and I want to move it to Prisma Postgres. At 1kb/request and $8/million requests, does that mean 150 million requests billed at $1200 just to get started?
Congrats on the launch, this looks very interesting!<p>Will it ever be possible to self-host Prisma Postgres (or Pulse)? It's great that I can use your platform, but if I adopted e.g. Pulse, that's a non-trivial vendor lock in. I'd feel _much_ safer/confident building my app around the Prisma stack (besides the ORM, which I like).
No offense but $0.09/GiB for DB read is so expensive. It sounds like servers would be querying Prisma over the internet? Then webmasters get to double pay their webhost for egress to the internet. Developers need to relearn how to self-host!
Anyone complaining here just isn't the target user. People who need an always available but zero maintenance and low usage seems to be the target user?<p>> always-on database with pay-as-you-go pricing for storage and queries (no fixed cost, no cost for compute). It's like a serverless database — but without cold starts and a generous free tier
> At Prisma, we believe that deploying a database should be as simple as adding a new page in Notion<p>I don't know what this means, but setting up a PostGres DB is a single PSQL command, or a few clicks in PgAdmin.
Drizzle [0] added an easter egg on their website in response to this announcement it seems.<p>[0]: <a href="https://orm.drizzle.team/" rel="nofollow">https://orm.drizzle.team/</a>
wow cool. Never heard about unikernels. Does it solve the issue with firecracker of not being able to reclaim memory? Would imagine that can be an issue for a long running app like a constantly busy database
Congratulations! Some innovation, some engineering. The other way, I was thinking about using uni kernels to deploy storage appliances via firecracker and here we go.