DatabasesComparison

Concurrency vs. Throughput: why more parallelism can make databases slower

From the source: PlanetScale Blog

Increasing throughput sometimes requires reducing parallelism. A look into why this is the case for Vitess + MySQL databases

Read the full story on PlanetScale Blog
Originally published by PlanetScale Blog on 7 Aug 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 →
DatabasesNew

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 →
DatabasesNew

Can your Postgres survive a bad query?

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

ClickHouse·via ClickHouse Blog
DatabasesNew

chDB Durable Layer for agent memory

The chDB Durable Layer keeps agent memory fast to query locally while making its analytical state recoverable across laptops, CI jobs, and short-lived sandboxes.

ClickHouse·via ClickHouse Blog
DatabasesHow-toWhy it matters

How to add hybrid search to a Postgres app with Pinecone in 2026

Add hybrid search to a Postgres app with Pinecone: full-text and vector search in one index, Postgres as the source of truth. Built around a snack shop example.

Pinecone·via Pinecone Blog
Databases

Who controls your intelligence analysis platform?

Over the years, I’ve seen two broad philosophies emerge for building an intelligence analysis platform. One concentrates knowledge and capability inside the vendor. The other builds them inside the customer’s own team. The distinction matters more as the platform grows.… Read more →

Neo4j·via Neo4j Blog