Handling hot shards

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 28 Sept, 00:00 UTC

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…