Menu

I Tested the Entire Prisma Platform on My Project: The Good, What Broke, and the Cloud Bill
📰

I Tested the Entire Prisma Platform on My Project: The Good, What Broke, and the Cloud Bill

DEV Community: nextjs·Aman Bind·about 11 hours ago
#oIEOZlVX
#devtonextjs#devto#dev#prisma#database
Long article (1742 words) — no AI summary yet.
Reading 0:00
15s threshold

A few months ago, I wrote an article titled “I Reduced Prisma Database Operations by 60% Without Upgrading My Database” . In that post, I shared how profiling slow queries with EXPLAIN ANALYZE helped us cut database operations on my project, Sellary ( sellary.in )—a digital commerce platform for Indian creators.

Shortly after publishing it, Martin Janse van Rensburg from the Prisma team reached out with an intriguing challenge:

"Since you already use Prisma ORM, would you be up for a follow-up running Sellary on the whole Prisma platform, adding Prisma Postgres and Prisma Compute , with an AI agent doing the setup?"

Martin offered two months of trial credits and asked for an honest, unfiltered take: setup experience, developer experience, latency, pricing, and what broke along the way.

As a solo developer running an independent project, my rule is simple: you never risk customer data or production uptime on an infrastructure experiment.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.