Menu

Prisma Accelerate shuts down Dec 1: what the URL swap misses (cacheStrategy, --no-engine, edge)
📰

Prisma Accelerate shuts down Dec 1: what the URL swap misses (cacheStrategy, --no-engine, edge)

DEV Community: postgres·Sunnatulla·about 12 hours ago
#497XNxfM
#devtopostgresql#devto#dev#prisma#accelerate
Reading 0:00
15s threshold

Prisma retires standalone Accelerate on December 1, 2026. The docs say it plainly on Keep your existing database , the Prisma Postgres guide says the hosted prisma+postgres://accelerate.prisma-data.net connection goes away the same day, and the October 2 changelog lists it under "What you need to do".

The obvious plan is to change DATABASE_URL , delete withAccelerate() and ship. For most of the apps I looked at, that isn't enough.

To see how often, I wrote a small offline checker and ran it on every public repo I could find that depends on @prisma/extension-accelerate . That was 35 repos. Two of them are Prisma's own examples and ecosystem tests, so I left those out of the counts below. Of the 33 actual apps, 23 need more than the URL, the import and the $extends call. I opened every finding in the source and checked it by hand.

Here is what the swap misses.

1. Edge routes that can't open a TCP connection (14 of 33 apps)

This is the most common one and the easiest to ship broken.…

Continue reading — create a free account

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