Data partitioning (sharding) jaqsam id-data fuq servers/databases multipli sabiex kull wieħed ikollu subset — li jippermettu l-horizontal scaling tad-data u l-load lil hinn minn server wieħed. L-għażla ta' kif tipartizzjonaw (il-partition key u l-strategy) hija kritika.
X'inhu partitioning/sharding
PARTITIONING / SHARDING → divide data into pieces (partitions/shards) across multiple
servers, each holding a SUBSET:
→ no single server holds (or is overwhelmed by) all the data
→ scales STORAGE and LOAD horizontally (each shard handles its portion)
→ enables handling data/throughput beyond one machine's capacity
Strateg ta' Partitioning
HASH-based → hash the partition key → assign to a shard:
✓ EVEN distribution (avoids hotspots) ✗ range queries hard; resharding is tricky
RANGE-based → partition by value ranges (e.g. A-M, N-Z; date ranges):
✓ efficient range queries ✗ risk of HOTSPOTS (uneven load if data/access is skewed)
DIRECTORY/lookup → a lookup table maps keys to shards (flexible, but the lookup is overhead)
GEOGRAPHIC → partition by region (data locality)
