{"id":23381,"date":"2025-11-12T14:29:25","date_gmt":"2025-11-12T14:29:25","guid":{"rendered":"https:\/\/pokecon.jp\/job\/?p=23381"},"modified":"2025-11-12T14:29:25","modified_gmt":"2025-11-12T14:29:25","slug":"should-you-stop-using-prisma-why-database-orms-might-be-the-worst-thing-that-happened-to-backend-development-by-sohail-saifi","status":"publish","type":"post","link":"https:\/\/pokecon.jp\/job\/23381\/","title":{"rendered":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi"},"content":{"rendered":"\n<\/p>\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
<\/p>\n
\n
\"Sohail<\/div>\n<\/div>\n

<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
Press enter or click to view image in full size<\/span><\/p>\n
\"\"<\/picture><\/div>\n<\/div>\n<\/figure>\n

I need to tell you something that might be controversial: Prisma, the darling of the TypeScript world, might be holding your application back.<\/strong><\/p>\n

After three years of using Prisma in production, debugging performance issues that shouldn\u2019t exist, and watching our serverless costs spiral out of control, I\u2019ve come to a painful realization. The same tool that promised to make database development easier has become our biggest bottleneck.<\/p>\n

But this isn\u2019t just about Prisma. This is about a fundamental problem with how we\u2019ve been thinking about database access in modern applications. ORMs promised us productivity and type safety, but they delivered complexity and performance issues we never asked for.<\/p>\n

Here\u2019s my journey from ORM evangelist to someone who thinks we took a seriously wrong turn.<\/p>\n

The Prisma Promise (And Why We All Fell for It)<\/h2>\n

Let\u2019s be honest \u2014 Prisma\u2019s marketing is brilliant. Type-safe database access! Automatic migrations! No more SQL! A single schema file that generates everything you need!<\/p>\n

When I first saw this code, I was sold:<\/p>\n

const users = await prisma.user.findMany({where: {email: {contains: 'john'}},include: {posts: {select: {title: true,createdAt: true}}}})<\/span><\/pre>\n
Clean, readable, type-safe. What could go wrong?<\/p>\n
Everything.<\/strong><\/p>\n
The Performance Reality Check<\/h2>\n
Here\u2019s what they don\u2019t tell you about Prisma: it\u2019s designed to be convenient, not fast.<\/p>\n
Let\u2019s talk numbers. According to benchmarks, Drizzle\u2019s bundle size is about 1.5 MB, while Prisma\u2019s bundle size is about 6.5 MB. In serverless environments, this matters. A lot.<\/p>\n
But bundle size is just the beginning. The real performance killer is what happens at runtime.<\/p>\n
The N+1 Problem on Steroids<\/h2>\n
Remember that innocent-looking query above? Here\u2019s what it actually does:<\/p>\n
-- First querySELECT * FROM users WHERE email LIKE '%john%';
-- Then for EACH user found:SELECT * FROM posts WHERE userId = 1;SELECT * FROM posts WHERE userId = 2;SELECT * FROM posts WHERE userId = 3;-- ... and so on<\/p><\/span><\/pre>\n
One logical query becomes dozens of database round trips. In one of our applications, what should have been a single JOIN query was generating 47 separate SQL statements.<\/p>\n
We moved to TanStack Query for our frontend state management to avoid this exact problem, only to recreate it in our backend with Prisma.<\/p>\n
The Serverless Nightmare<\/h2>\n
Our AWS Lambda cold starts went from 200ms to 2.5 seconds after introducing Prisma. Why? Because Prisma needs to:<\/p>\n
    \n
  1. Load the Rust-based query engine binary<\/li>\n
  2. Start an internal GraphQL server<\/li>\n
  3. Initialize connection pooling<\/li>\n
  4. Generate the client interface<\/li>\n<\/ol>\n
    All of this happens before your function can even start processing the request.<\/p>\n
    As one developer put it: \u201cPrisma happens to have a lot of content that you can find on this topic specifically, but the problem stems from cold starts in certain serverless environments like AWS Lambda. With Drizzle being such a lightweight solution, the time required to load and execute a serverless function or Lambda will be much quicker than Prisma.\u201d<\/p>\n
    The Developer Experience Mirage<\/h2>\n
    Prisma\u2019s biggest selling point is Developer Experience (DX). But here\u2019s the dirty secret: great DX for simple things often means terrible DX for complex things.<\/strong><\/p>\n
    The Schema Lock-In<\/h2>\n
    Everything in Prisma revolves around the schema.prisma<\/code> file. It’s your single source of truth, they say. But what happens when you need to do something that doesn’t fit neatly into Prisma’s DSL?<\/p>\n
    Want to use database-specific features like PostgreSQL\u2019s JSONB operators? Good luck. Need to write a complex query with CTEs? You\u2019re back to raw SQL, but now you\u2019re mixing paradigms and losing all the type safety you supposedly gained.<\/p>\n
    As one frustrated developer noted: \u201cAll the boilerplate and the files for redux remain the reason why I haven\u2019t used it extensively, so many moving parts.\u201d The same applies to Prisma \u2014 it promises simplicity but delivers complexity.<\/p>\n
    The Generation Dance<\/h2>\n
    Every time you change your schema, you have to run prisma generate<\/code>. This regenerates thousands of lines of TypeScript code. Your IDE freezes. Your build process slows down. And heaven forbid you forget to run it – now your types are out of sync with your database.<\/p>\n
    Contrast this with Drizzle, where changes to your schema are immediately reflected because everything is just TypeScript. No code generation, no waiting, no extra steps.<\/p>\n
    The Migration Nightmare<\/h2>\n
    Prisma\u2019s migration system looks great in demos. In production, it\u2019s a different story.<\/p>\n
    Data Loss by Design<\/h2>\n
    Here\u2019s something that actually happened to us: we renamed a column in our schema. Prisma\u2019s migration system didn\u2019t detect it as a rename \u2014 it treated it as dropping the old column and creating a new one.<\/p>\n
    All the data in that column was gone.<\/strong><\/p>\n
    Drizzle handles this better. When it detects a possible renaming, it enters interactive mode and lets you choose your intention. Prisma? It just drops your data and generates a \u201chelpful\u201d warning about potential data loss.<\/p>\n
    The Black Box Problem<\/h2>\n
    Prisma generates SQL migrations for you, but they\u2019re often not what you\u2019d write by hand. They\u2019re verbose, sometimes inefficient, and hard to review. When you need to customize a migration, you\u2019re fighting against the tool instead of working with it.<\/p>\n
    The Real Cost of Abstraction<\/h2>\n
    Ted Neward called ORMs \u201cthe Vietnam War of computer science\u201d back in 2008. His words were prophetic: \u201ca quagmire which starts well, gets more complicated as time passes, and before long entraps its users in a commitment that has no clear demarcation point, no clear win conditions, and no clear exit strategy.\u201d<\/p>\n
    ORMs promise to eliminate the \u201cimpedance mismatch\u201d between object-oriented code and relational databases. But here\u2019s the thing: they don\u2019t eliminate it. They hide it.<\/strong><\/p>\n
    And when that abstraction leaks (which it always does), you\u2019re worse off than when you started because now you need to understand both your ORM\u2019s quirks AND the SQL it generates.<\/p>\n
    What Smart Developers Are Using Instead<\/h2>\n
    After our Prisma experience, we evaluated alternatives. Here\u2019s what we found:<\/p>\n
    Drizzle: The TypeScript-Native Approach<\/h2>\n
    Drizzle calls itself \u201cIf you know SQL, you know Drizzle.\u201d And it\u2019s true:<\/p>\n
    const users = await db.select().from(usersTable).where(like(usersTable.email, '%john%')).leftJoin(postsTable, eq(usersTable.id, postsTable.userId));<\/span><\/pre>\n
    This is SQL, but with full TypeScript safety. No code generation. No binaries. No magic.<\/p>\n
    Performance? Drizzle is orders of magnitude faster than Prisma in benchmarks. Bundle size? 1.5MB vs Prisma\u2019s 6.5MB.<\/p>\n
    Raw SQL with Type Safety<\/h2>\n
    Tools like SQLx in Rust show us what\u2019s possible: compile-time checked SQL queries with zero runtime overhead.<\/p>\n
    In TypeScript, libraries like Kysely provide similar benefits:<\/p>\n
    const users = await db.selectFrom('users').leftJoin('posts', 'users.id', 'posts.userId').select(['users.name', 'posts.title']).where('users.email', 'like', '%john%').execute();<\/span><\/pre>\n
    It\u2019s still SQL, but with TypeScript safety and IDE support.<\/p>\n
    The \u201cRaw SQL is Actually Better\u201d Movement<\/h2>\n
    More developers are returning to raw SQL. Why? Because:<\/p>\n
      \n
    1. It\u2019s more transparent<\/strong> \u2014 you know exactly what queries are running<\/li>\n
    2. It\u2019s more performant<\/strong> \u2014 no abstraction overhead<\/li>\n
    3. It\u2019s more portable<\/strong> \u2014 SQL knowledge transfers between projects<\/li>\n
    4. It\u2019s more secure<\/strong> \u2014 you\u2019re aware of injection risks, making you more careful<\/li>\n<\/ol>\n
      As one developer put it: \u201cI\u2019d argue that a 20-line SQL query is way easier to understand than trying to figure out what some ORM method chain is gonna generate. Plus, SQL is standardized \u2014 any developer can read it.\u201d<\/p>\n
      The Security Implications Nobody Talks About<\/h2>\n
      ORMs are supposed to be more secure because they prevent SQL injection. But they introduce new security problems:<\/p>\n
      Mass Assignment Vulnerabilities<\/h2>\n
      This Prisma code looks safe:<\/p>\n
      app.post('\/users', async (req, res) => {const user = await prisma.user.create({data: req.body});});<\/span><\/pre>\n
      But what if the request body includes a role: 'admin'<\/code> field you didn’t expect? Congratulations, you just created an admin user.<\/p>\n
      With raw SQL, this pattern is much less likely because you explicitly specify which fields to update.<\/p>\n
      Excessive Database Permissions<\/h2>\n
      ORMs often require broader database permissions to function. They need to query table schema information, access metadata, and perform reflection. This violates the principle of least privilege.<\/p>\n
      The Bundle Size Problem<\/h2>\n
      In 2024, we care about bundle sizes. Frameworks like Astro and SvelteKit emphasize minimal JavaScript. But then we add 6.5MB ORMs to our backend.<\/p>\n
      For edge computing and serverless functions, every kilobyte matters. Cloudflare\u2019s free plan has a 3MB limit. Prisma eats up more than half of that before you write a single line of business logic.<\/p>\n
      When ORMs Still Make Sense<\/h2>\n
      I\u2019m not saying ORMs are always wrong. There are cases where they shine:<\/p>\n
      Rapid Prototyping<\/strong>: When you need to get something working quickly and performance isn\u2019t critical.<\/p>\n
      Junior Teams<\/strong>: If your team doesn\u2019t have strong SQL skills, an ORM can provide guardrails.<\/p>\n
      Simple CRUD Applications<\/strong>: For basic create\/read\/update\/delete operations without complex relationships.<\/p>\n
      Enterprise Requirements<\/strong>: Some organizations mandate ORMs for compliance or standardization reasons.<\/p>\n
      But for most production applications, the costs outweigh the benefits.<\/p>\n
      The Path Forward<\/h2>\n
      If you\u2019re thinking about moving away from ORMs, here\u2019s a migration strategy:<\/p>\n
      1. Start with New Features<\/h2>\n
      Don\u2019t rewrite everything at once. Build new features with your chosen alternative (Drizzle, Kysely, or raw SQL) and see how it feels.<\/p>\n
      2. Identify Performance Bottlenecks<\/h2>\n
      Use profiling to find your slowest database operations. These are good candidates for migration because you\u2019ll see immediate improvements.<\/p>\n
      3. Migrate One Domain at a Time<\/h2>\n
      Pick a bounded context in your application and migrate all its database access together. This maintains consistency within domains.<\/p>\n
      4. Invest in Tooling<\/h2>\n
      Set up proper database migration tools, query builders, and type generation. The initial setup takes time, but you\u2019ll be more productive in the long run.<\/p>\n
      The Bottom Line<\/h2>\n
      Prisma isn\u2019t inherently evil. It\u2019s a well-engineered tool that solves real problems. But it also creates new problems that many teams don\u2019t anticipate.<\/p>\n
      The question isn\u2019t whether Prisma is good or bad. The question is whether the problems it solves are worth the problems it creates for YOUR application.<\/p>\n
      In our case, the answer was no. Moving away from Prisma reduced our serverless costs by 40%, improved our performance by 3x, and made our codebase more maintainable.<\/p>\n
      But more importantly, it forced us to understand our database better. We stopped treating it as a dumb storage layer and started leveraging its power. Our queries became more efficient. Our data models became cleaner. Our debugging sessions became shorter.<\/p>\n
      ORMs promised to make us more productive by hiding complexity. But as it turns out, the complexity was never hidden \u2014 it was just moved to a place where we couldn\u2019t see it until it was too late.<\/strong><\/p>\n
      Maybe it\u2019s time to stop hiding from our databases and start embracing them.<\/p>\n<\/div>\n\n
      \u5143\u306e\u8a18\u4e8b\u3092\u78ba\u8a8d\u3059\u308b <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Press enter or click to view image in full size I need to tell you something that might be controversial: Pris […]","protected":false},"author":1,"featured_media":23382,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-23381","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hatena-blog"],"acf":[],"yoast_head":"\nShould You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"og:description\" content=\"Press enter or click to view image in full size I need to tell you something that might be controversial: Pris […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846\" \/>\n<meta property=\"og:site_name\" content=\"\u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-12T14:29:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1000\" \/>\n\t<meta property=\"og:image:height\" content=\"500\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"info@pokecon.jp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"info@pokecon.jp\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"9\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/23381\\\/\"},\"author\":{\"name\":\"info@pokecon.jp\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"headline\":\"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi\",\"datePublished\":\"2025-11-12T14:29:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/23381\\\/\"},\"wordCount\":1696,\"image\":{\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/wp-content\\\/uploads\\\/2025\\\/11\\\/0KLm_jYDWCgDLm7Cv.png\",\"articleSection\":[\"\u306f\u3066\u306a\u30d6\u30ed\u30b0\"],\"inLanguage\":\"ja\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/23381\\\/\",\"url\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846\",\"name\":\"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/wp-content\\\/uploads\\\/2025\\\/11\\\/0KLm_jYDWCgDLm7Cv.png\",\"datePublished\":\"2025-11-12T14:29:25+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#primaryimage\",\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/wp-content\\\/uploads\\\/2025\\\/11\\\/0KLm_jYDWCgDLm7Cv.png\",\"contentUrl\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/wp-content\\\/uploads\\\/2025\\\/11\\\/0KLm_jYDWCgDLm7Cv.png\",\"width\":1000,\"height\":500},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/medium.com\\\/@sohail_saifi\\\/should-you-stop-using-prisma-421aba045846#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u30db\u30fc\u30e0\",\"item\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\",\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\",\"name\":\"\u30dd\u30b1\u30b3\u30f3\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\",\"name\":\"info@pokecon.jp\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"caption\":\"info@pokecon.jp\"},\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/author\\\/infopokecon-jp\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846","og_locale":"ja_JP","og_type":"article","og_title":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3","og_description":"Press enter or click to view image in full size I need to tell you something that might be controversial: Pris […]","og_url":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846","og_site_name":"\u30dd\u30b1\u30b3\u30f3","article_published_time":"2025-11-12T14:29:25+00:00","og_image":[{"width":1000,"height":500,"url":"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png","type":"image\/png"}],"author":"info@pokecon.jp","twitter_card":"summary_large_image","twitter_misc":{"\u57f7\u7b46\u8005":"info@pokecon.jp","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"9\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#article","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/23381\/"},"author":{"name":"info@pokecon.jp","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"headline":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi","datePublished":"2025-11-12T14:29:25+00:00","mainEntityOfPage":{"@id":"https:\/\/pokecon.jp\/job\/23381\/"},"wordCount":1696,"image":{"@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#primaryimage"},"thumbnailUrl":"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png","articleSection":["\u306f\u3066\u306a\u30d6\u30ed\u30b0"],"inLanguage":"ja"},{"@type":"WebPage","@id":"https:\/\/pokecon.jp\/job\/23381\/","url":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846","name":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi - \u30dd\u30b1\u30b3\u30f3","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/#website"},"primaryImageOfPage":{"@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#primaryimage"},"image":{"@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#primaryimage"},"thumbnailUrl":"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png","datePublished":"2025-11-12T14:29:25+00:00","author":{"@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"breadcrumb":{"@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846"]}]},{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#primaryimage","url":"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png","contentUrl":"https:\/\/pokecon.jp\/job\/wp-content\/uploads\/2025\/11\/0KLm_jYDWCgDLm7Cv.png","width":1000,"height":500},{"@type":"BreadcrumbList","@id":"https:\/\/medium.com\/@sohail_saifi\/should-you-stop-using-prisma-421aba045846#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u30db\u30fc\u30e0","item":"https:\/\/pokecon.jp\/job\/"},{"@type":"ListItem","position":2,"name":"Should You Stop Using Prisma? Why Database ORMs Might Be the Worst Thing That Happened to Backend Development | by Sohail Saifi"}]},{"@type":"WebSite","@id":"https:\/\/pokecon.jp\/job\/#website","url":"https:\/\/pokecon.jp\/job\/","name":"\u30dd\u30b1\u30b3\u30f3","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/pokecon.jp\/job\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997","name":"info@pokecon.jp","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","caption":"info@pokecon.jp"},"url":"https:\/\/pokecon.jp\/job\/author\/infopokecon-jp\/"}]}},"_links":{"self":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/23381","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/comments?post=23381"}],"version-history":[{"count":1,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/23381\/revisions"}],"predecessor-version":[{"id":23383,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/23381\/revisions\/23383"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/media\/23382"}],"wp:attachment":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/media?parent=23381"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/categories?post=23381"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/tags?post=23381"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}