Designing Neki for performance

From the source: PlanetScale Blog

How Neki only decodes the parts of a PostgreSQL result the router actually needs.

Read the full story on PlanetScale Blog
Originally published by PlanetScale Blog on 1 Oct 2026. Techarda links to the original rather than republishing it. Read the full article →

Have you worked with this?

The story is what was announced. Nobody has discussed it yet, so if it touches your team, a short post about what you’ve seen helps the next reader.

Start the discussion

More from PlanetScale

Recent updates from PlanetScale, so you can tell whether this is a one-off or part of a pattern.

All PlanetScale news →
Databases

Handling hot shards

What makes a good sharding strategy today might not work so well tomorrow. What happens when you have one tenant hitting your database orders of magnitude more than any other? Or product managers knocking down your door with new requirements? If you're already on Neki, fortunately these are issues we can solve.

PlanetScale·via PlanetScale Blog
DatabasesComparison

When to choose x86-64 vs aarch64

ARM and x86 can give you different performance at the same vCPU count. Here's what differs, what to measure, and how to choose.

PlanetScale·via PlanetScale Blog
Databases

TIN Postgres search is faster, better, and cheaper

A good Postgres search demo was doing the rounds online. Let's see what happens when we upgrade it to TIN.

PlanetScale·via PlanetScale Blog

More in Databases

What other companies in Databases are doing. The category page shows who’s active, side by side.

Compare companies in Databases →
Databases

How LinkedIn extended ClickHouse from distributed tracing to metric discovery and analytics

LinkedIn expanded its ClickHouse observability stack from distributed tracing to metric discovery and analytics, consolidating 13B+ metrics into one index serving 150k+ queries per minute.

ClickHouse·via ClickHouse Blog
Databases

What is direct I/O, and why does ClickHouse Managed Postgres use it for backups?

ClickHouse Managed Postgres uses direct I/O and stripe-sized reads to keep backups fast while protecting the page cache and query latency.

ClickHouse·via ClickHouse Blog
DatabasesCase study

How Jev Uses Meko to Make Code Review Feedback Stick

When a Jev-powered check gets something wrong, and a person corrects it, where does that correction go, and how can you ensure the correction is implemented in future results? This blog explains why a decision model correction should live outside the model, what a system needs to ensure corrections carry into the next request, and the code review check that prevents the system from raising a…

Yugabyte·via Yugabyte Blog
Databases

Beyond the return: who controls the business?

A tax return can be correct and still tell the authority too little. The filing identifies the taxpayer but it may not reveal who actually controls the business. Investigations into tax fraud and related financial crime often depend on some… Read more →

Neo4j·via Neo4j Blog