-
Notifications
You must be signed in to change notification settings - Fork 903
feat(blog): sunsetting optimise #7690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+218
−0
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
59 changes: 59 additions & 0 deletions
59
apps/blog/content/blog/sunsetting-prisma-optimize/index.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| --- | ||
| title: "Sunsetting Prisma Optimize" | ||
| slug: "sunsetting-prisma-optimize" | ||
| date: "2026-03-23" | ||
| authors: | ||
| - "Mike Hartington" | ||
| metaTitle: "Sunsetting Prisma Optimize" | ||
| metaDescription: "Prisma Optimize is being sunset as we move query observability directly into Prisma Postgres through Query Insights." | ||
| heroImagePath: "/sunsetting-prisma-optimize/imgs/optimize-sunset.svg" | ||
| metaImagePath: "/sunsetting-prisma-optimize/imgs/optimize-sunset@2x.png" | ||
| tags: | ||
| - "announcement" | ||
| - "prisma-postgres" | ||
| --- | ||
|
|
||
| We're sunsetting Prisma Optimize to make room for Query Insights. Query Insights is built right into Prisma Postgres and removes the friction that Optimize introduced. Let's look into what lead us to this decision and what this means for your projects. | ||
|
|
||
| ## What we learned from Prisma Optimize | ||
|
|
||
| In recent rounds of user feedback, we asked users of Optimize what their pain points were with the feature. In those conversations, a few patterns became clear: | ||
|
|
||
| - **Adding a client extension for monitoring introduced friction**, especially across runtimes and environments. | ||
| - **Visibility into SQL queries was limited**, and teams wanted more direct insight into what was happening at the database level. | ||
| - **AI recommendations lacked SQL context**, which made it harder to connect suggestions to the underlying query behavior. | ||
| - **Profiling felt too manual**, with recording workflows that were heavy for quick investigations. | ||
|
|
||
| All of this pointed to the same conclusion: **query observability should be automatic, not something you have to wire up yourself.** | ||
|
|
||
| ## Introducing Query Insights | ||
|
|
||
| **Query Insights** is built directly into **Prisma Postgres** and automatically provides analytics about your queries without requiring client extensions or additional setup. | ||
|
|
||
| Simply open your Prisma Postgres dashboard and go to the Queries tab. | ||
|
|
||
|  | ||
|
|
||
| ## For existing Prisma Optimize users | ||
|
|
||
| If you previously installed Prisma Optimize, you can safely remove it. | ||
|
|
||
| 1. Uninstall the package: | ||
|
|
||
| ```npm | ||
| npm uninstall @prisma/extension-optimize | ||
| ``` | ||
|
|
||
| 2. Remove the extension from your Prisma Client setup: | ||
|
|
||
| ```typescript diff | ||
| import { PrismaClient } from '@prisma/client' | ||
| -import { withOptimize } from '@prisma/extension-optimize' | ||
|
|
||
| const prisma = new PrismaClient() | ||
| .$extends(withOptimize()) // [!code --] | ||
| ``` | ||
|
|
||
| Query Insights is available now as part of **Prisma Postgres** without extra setup, and will be launching more broadly soon. | ||
|
|
||
| Stay tuned for the official launch. | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.