feat(blog): Prisma Next performance benchmark post

[ankur-arch]

Summary

• Adds new Prisma Next performance deep dive blog post by Serhii Tatarintsev (seriesIndex: 9)
• Benchmarks Prisma Next vs Prisma 7 vs raw pg driver — ~50% higher peak throughput, 9x smaller bundle
• Moves hero/meta images (2 _ Bars panel.svg/.png) and three benchmark SVGs into public/prisma-next-performance-benchmark/imgs/
• Adds Serhii Tatarintsev author photo to public/authors/

Test plan

• Verify blog post renders at /blog/prisma-next-performance-benchmark
• Confirm hero image, meta image, and all three benchmark SVGs load correctly
• Verify author photo and name display correctly
• Confirm post appears in the Prisma Next series at index 9

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added new blog post with Prisma Next performance benchmarks, comparing throughput, latency, and bundle size against Prisma 7 and the pg driver.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 11, 2026 10:48am
docs	Ready	Preview, Comment	Jun 11, 2026 10:48am
eclipse	Ready	Preview, Comment	Jun 11, 2026 10:48am
site	Ready	Preview, Comment	Jun 11, 2026 10:48am

[coderabbitai]

Walkthrough

This PR introduces a new performance benchmark blog post comparing Prisma Next against Prisma 7 and the raw pg driver. The post includes frontmatter metadata, benchmark methodology, peak throughput and latency results with tables and visualizations, bundle size analysis, and guidance on practical implications and limitations.

Changes

Performance Benchmark Blog Post

Layer / File(s)	Summary
Post metadata and headline takeaways apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx	MDX frontmatter with publication metadata and opening narrative that summarizes headline results: throughput improvements, latency characteristics, relative peak performance versus pg, and Early Access note.
Benchmark methodology and throughput results apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx	"How we ran the benchmark" section describing the fork of an existing workload, load generator approach, and raw pg baseline; "Peak throughput" section with explanation, figures, and a table comparing sustained throughput across pg, Prisma Next, and Prisma 7.
Latency analysis, bundle size, and implications apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx	"Latency at the same load" section with fair-comparison guidance, latency table (avg/p95/p99), text on scaling behavior, and p95-over-time chart; "Bundle size" section with gzip figures and cold-start commentary; "What this means for your app" with key takeaways and scope caveats; "Limitations and what's next" with single-workload/machine caveats and links to repo and resources.

---

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat(blog): Prisma Next performance benchmark post' directly and clearly describes the main change: adding a new blog post about Prisma Next performance benchmarking.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jun 11, 2026, 10:54 AM

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx (1)

51-51: 💤 Low value

Chart alt text uses different rounding than table and opening.

The alt text states "Prisma Next ~12,534" and "Prisma 7 ~8,260," but the opening paragraph (line 25) and table (lines 56-57) use "~12,500" and "~8,300." While both are approximations, using consistent rounding across all references improves clarity and reduces reader confusion.

Consider updating the alt text to match the rounded figures used elsewhere, or updating the table/opening to match the precise figures from the chart.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx` at line
51, The image alt text line containing "Peak sustained throughput: pg ~14,350
req/s, Prisma Next ~12,534 (87% of pg), Prisma 7 ~8,260 (58% of pg)" should use
the same rounding as the opening paragraph and table; update that alt string to
"Peak sustained throughput: pg ~14,350 req/s, Prisma Next ~12,500 (87% of pg),
Prisma 7 ~8,300 (58% of pg)" (or alternatively adjust the opening/table to the
precise chart values) so all references are consistent; locate and edit the
markdown image tag string shown in the diff to make the change.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx`:
- Line 50: The sentence that currently reads "flattening just under 8,000 req/s"
should be updated to match the more precise Prisma 7 throughput cited elsewhere
(≈8,260–8,300 req/s); replace that phrase with "flattening around 8,300 req/s"
(or "around 8,260 req/s" if you prefer the chart value) so the line matches the
opening paragraph, chart alt text, and table; locate the exact string
"flattening just under 8,000 req/s" in the post and change it accordingly.
- Line 21: Replace the broken external link "https://pris.ly/pn-benchmarks" with
the valid Prisma Next URL "https://pris.ly/pn-series" wherever it appears in the
content (e.g., the sentence referencing "Prisma Next"); update both occurrences
so the link resolves correctly.
- Line 10: The blog frontmatter schema is missing heroImageAlt which is present
in the MDX and read as data.heroImageAlt; update the frontmatter schema in
apps/blog/source.config.ts to add a heroImageAlt string field (make it optional
if not all posts will have it) and update any associated TypeScript type or Zod
schema used for validation so that imageAlt access (data.heroImageAlt) is
type-safe; alternatively remove the heroImageAlt line from the MDX file if you
prefer not to support it.

---

Nitpick comments:
In `@apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx`:
- Line 51: The image alt text line containing "Peak sustained throughput: pg
~14,350 req/s, Prisma Next ~12,534 (87% of pg), Prisma 7 ~8,260 (58% of pg)"
should use the same rounding as the opening paragraph and table; update that alt
string to "Peak sustained throughput: pg ~14,350 req/s, Prisma Next ~12,500 (87%
of pg), Prisma 7 ~8,300 (58% of pg)" (or alternatively adjust the opening/table
to the precise chart values) so all references are consistent; locate and edit
the markdown image tag string shown in the diff to make the change.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9a081213-0e56-47c2-be05-a630efd23351

📥 Commits

Reviewing files that changed from the base of the PR and between 0ef6b0c and bf31198.

⛔ Files ignored due to path filters (6)

• apps/blog/public/authors/serhii-tatarintsev.png is excluded by !**/*.png
• apps/blog/public/prisma-next-performance-benchmark/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-next-performance-benchmark/imgs/latency-over-time.svg is excluded by !**/*.svg
• apps/blog/public/prisma-next-performance-benchmark/imgs/meta.png is excluded by !**/*.png
• apps/blog/public/prisma-next-performance-benchmark/imgs/peak-throughput.svg is excluded by !**/*.svg
• apps/blog/public/prisma-next-performance-benchmark/imgs/throughput-ramp.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx