Handling hot shards
From the source: PlanetScale BlogWhat 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.
Read the full story on PlanetScale BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Databases
Postgres everywhere vs purpose-built databases: where do you draw the line?
Vector search, time series, queues, analytics: many teams now start with Postgres extensions. Where has that worked, and where did you need a dedicated engine?
What is your approach to zero-downtime schema migrations at scale?
Expand-and-contract, online schema change tools, feature flags? Share what has kept large-table migrations boring.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from PlanetScale
Recent updates from PlanetScale, so you can tell whether this is a one-off or part of a pattern.
More in Databases
What other companies in Databases are doing. The category page shows who’s active, side by side.



