It is a classic trap: you spend a week fine-tuning your cache and your database hits only to realize your application is essentially running with the handbrake on. I saw this with my tests: MySQL and Readyset were returning rows in 0.2 ms, but the application throughput remained capped at 40 queries per second (QPS).

The database isn’t the bottleneck, and the cache isn’t the bottleneck. Your application code is simply leaving performance on the table. While running some demos recently, I found that a Node.js service went from 40 QPS to over 6,000 QPS, which is a 150x improvement without changing a single database setting or query plan. Here is a post-mortem of how application-layer bottlenecks can neutralize even the most aggressive infrastructure wins.

The “Fairness” Trap: Event Loop Lag

In Node.js and similar async runtimes we are taught to “be …

In my recent series on Scoped Vector Search, we looked at the query patterns that make vector search a first-class citizen in MySQL. While the logic for those searches is now established, the infrastructure supporting them requires constant attention as the MySQL ecosystem moves toward its new release model.

Today, I’m announcing MyVector v1.26.3. This is a foundational release focused on environment compatibility and CI/CD robustness.

What’s in v1.26.3?

This release ensures that MyVector remains stable and buildable across the shifting landscape of MySQL Innovation and LTS releases.

• MySQL 8.4 & 9.6 Compatibility: We’ve updated the component sources and build logic to align with the headers and …

Moving from Ops Insights/Database Management to OCI Monitoring and Unified Log Analytics OCI is updating the recommended approach for observing MySQL HeatWave. This includes changes to existing integrations, along with a path forward that provides stronger log analytics and AI-assisted analysis—while continuing to use OCI Monitoring as the foundational layer for metrics and alarms. What’s […]

This is a quick one.  My attention was recently brought (thanks Simon) on a relatively recent comment (25 Nov 2025) in Bug #103672 - Binlog compression transaction payload event exceeds max allowed packet :

The underlying server bug was fixed in 8.0.34 in BUG#33588473. The server now falls back to writing the transaction without compression, if the compressed size would

In the world of database management, MySQL HeatWave offers powerful in-memory analytics capabilities that can supercharge your OLTP queries. But what happens when you introduce views into the mix? A common question I get is: “If I create a view in MySQL, does this view run against the data stored in the tables in HeatWave […]

MySQL observability is essential in modern enterprises, whether you run a few critical databases or operate at massive scale. With the right real‑time monitoring, teams reduce MTTD/MTTR, avoid cascading failures, and continuously track workload health—CPU, memory, I/O, buffer pool efficiency, session contention, transaction/replication lag, error rates, and query latency. This Grafana monitoring template helps teams […]

On March 23, 2026, the MySQL Community Team hosted our second public discussion focused on shaping a new era of MySQL community engagement. With over 50 attendees participating, the session brought together members of the MySQL ecosystem to share feedback, discuss priorities, and help guide future efforts. Building on our earlier session, this webinar continued […]

We're excited to announce that PlanetScale is participating as a co-design and launch partner for Stripe Projects, a new developer preview from Stripe that centralizes dev tool provisioning and billing in one place.

What is Stripe Projects?

Stripe Projects is a new way for developers and coding agents to discover, provision, and pay for developer tools all from the Stripe CLI. Instead of jumping between dashboards, entering payment info, and copying credentials across services, everything lives in one centralized workflow.

This fragmented developer workflow has always existed, but AI agents have made the gap much more obvious. The ecosystem has been missing a standard way for provisioning and credential handoff to work reliably across …

Practical guide to reducing MySQL data bloat through three archiving approaches: controlled deletes, partitioning, and replication-based offloading, with trade-offs and operational considerations.Tags: archivingpartitioningperformance

Last week, we published MySQL Early Access Release builds available for community testing and feedback ahead of the upcoming stable releases. Early Access builds are ideal for developers and DBAs who want to validate compatibility, behavior, and performance in non-production environments—and help us catch regressions early or identify areas where the documentation could be clearer. We […]