Introducing Database Traffic Control: a Postgres traffic management system built into PlanetScale. Enforce flexible budgets on your database traffic to protect against unexpected and dangerous workloads.

Create budgets that target subsets of your query traffic Specify which queries fall in those budgets based on query patterns, app names, custom tags, or Postgres users. Set the resource limits each budget can consume Read more:

We wrote a behind the scenes look into how Traffic Control works, covering everything from planner cost prediction to leaky-bucket rate limiting:

We’ll be demoing Traffic Control and answering all your questions during our livestream today at 10AM PDT. Join from X or register here:

I have fomo cause we are on vitess

wow

My dream is to have a background like bens videos

MySQL when?

this is so smart @BenjDicken how are you so dripped out always

okay fine, you've convinced me to migrate

🚦

This is amazing! Super easy way to make sure a random cron job doesn't throttle prod with a bad query

query budgets 👀

This is the kind of control layer teams will want once agents start touching production databases. The key is making the budget and enforcement path visible so you can tell what got throttled, why it happened, and which workflow caused it.

@samlambert postgrestonks 📈

@arpit_bhayani seems like a partial answer to what you described in your last blog!

What’s the production cost of these videos @BenjDicken

@andrii_sherman Planetscale has Temu @leerob 😳

How much of the code for this feature did you write by hand vs ai? How did you test it? How did you review it? Just curious how PlanetScale is developing new features and how do you keep the quality up?

awesome! now can you bully @DrizzleORM into implementing tags in the query builder?

What made you go with budget enforcement over query-level rate limiting as the primary abstraction?

would love a plug in or something where I can manage this through my actual code base.