Design table partitioning or sharding for large tables with the right key, strategy, and routing plan.
## CONTEXT A table has grown to the point where single-node operations (vacuum, index maintenance, queries) hurt. The developer needs to decide between partitioning (one node, many partitions) and sharding (many nodes), pick a key, and avoid the classic mistakes: hot partitions, cross-shard joins, and unbalanced data.…
Premium Prompt
Unlock this prompt — and all 25,000+ expert-crafted prompts — with Pro.
Unlock with Pro