But then we started using Bun in anger, and we found many memory leaks in the Bun internals, that we knew our customers would face as well. Prisma Compute is operating long-running services, utilising memory snapshots to pause the instance when not in use. We need these Bun instances to be able to reliably serve customer workloads for days and months.

We were able to fix some of these memory leaks directly in the code base, but getting the patches upstreamed proved difficult. And running on a fork with an ever increasing number of patches wasn't an appealing option.

And then as our Beta launch approached, Jarred announced the big rewrite (prior discussion: https://news.ycombinator.com/item?id=48132488)

We have found that the rewrite directly addresses several of the memory leaks we had identified. And we have found the new Rust codebase to be easier to contribute to. So we made the decision to launch on Bun Canary and do whatever we can to help improve Bun.

We wrote about it here, and you can have your agent of choice deploy an app in just a couple minutes if you want to give it a try. It's Beta, so we are still busy polishing the experience: https://www.prisma.io/blog/launching-prisma-compute-public-beta