PWV Portfolio Feed

(credit to @samwho.dev for mentioning this!)

The result:

⚡ 0.1–1ms -> 1–10µs per query
📈 Higher throughput
📉 Lower latency
🎯 ~100% cache hit rate in typical apps

Under concurrency, the difference is significant.

In v7.4, we introduced a schema-aware query caching layer.

Instead of having to rebuild your query on every run, Prisma now:

• Parameterizes dynamic values
• Reuses the static query structure
• Avoids repeated compilation work

In v6, queries happened in a separate Rust-based thread.
In v7, queries happens in the JavaScript event loop.

Individually, each query is able to run fast (0.1–1ms per query).

Under load though, there is an increase in latency due to the single threaded nature of the JavaScript

When we shipped Prisma ORM v7, we moved away from Rust to simplify the architecture and invest in long-term flexibility.

But it came with a trade-off: performance under high concurrency.

You can use prisma debug to quickly see the exact runtime context that helps troubleshoot Prisma issues, including config and schema paths, engine cache location, env var status, and whether CI/interactive mode is detected.

Node.js 24 changed how `events.once()` cleans up listeners

nobody told my teardown function

wasted a bunch of time today fixing tests. 

eng workflows need to change with fast changing software.

the best code you write this week will probably be a deletion

not a clever abstraction. not a new feature. one line removed from a teardown function that was quietly causing exit code 1 after passing tests.

subtraction is underrated in engineering. it's underrated in startups too.

Chunks are now entry-aware in Rolldown 1.0.0-rc.5 ⚡

What does that mean? When grouping chunks via `codeSplitting`, they can now be automatically split per entry point (usually per page), so users download less unused JavaScript.

Just set `entriesAware: true`.

we're working on it! 👍