Removed Rust to Gain Speed

Summary

Designed for the future In December 2024, we published our vision for the future of Prisma ORM along with the steps we planned to take to achieve it. This was not just a set of ideas. It was a clear commitment to how we want Prisma ORM to evolve and how we intend to support the community along the way. We also launched our own managed Postgres offering, Prisma Postgres. Built with simplicity and performance in mind, we wanted to provide an easy-to-adopt database that would bring all of the developer experience you know and love from Prisma ORM. With the ORM roadmap and Prisma Postgres launched, we had a solid foundation for how to build the next version of each tool. The response to both of these products has been stellar. We see significant growth in the ORM market share and usage, and Prisma Postgres' hobby and commercial adoption has been spectacular. Moving away from Rust When we launched 6.0.0, we promised better performance, more flexibility, and better type-safety. We knew there was work to be done, and to get there, we needed to make some drastic changes. We announced we were migrating the Prisma Client away from Rust and rebuilding it in TypeScript. This might have seemed like a strange move to some, as Rust’s main premise is that it is fast and performant. But that is only half the story in our case. A side effect of the client being built in Rust is that we were limiting who can contribute to the ORM. If you didn’t have strong Rust experience, it was far more difficult to make any meaningful contributions. On the technical side, the communication layer between Rust and the JavaScript runtime is much slower than doing things in plain JavaScript, plus it creates additional dependencies on the runtime. Our friends at Deno shared this sentiment: “We remember hearing about Prisma’s move away from Rust and thinking about how not dealing with the native addon API would make supporting Prisma in Deno so much simpler. We were all really excited to see it!"Luca Cas...