Sharding a database is a common scalability strategy for designing server-side systems. The server-side system architecture uses concepts like sharding to make systems more scalable, reliable, and performant.
Sharding is the horizontal partitioning of data according to a shard key. This shard key determines which database the entry to be persisted is sent to. Some common strategies for this are reverse proxies.
Database interviews ask for concepts like sharding to make databases more performant and available. This makes horizontal partitioning a logical choice.
Looking to ace your next interview? Try this System Design video course! 🔥
interviewready.io
00:00 Introduction
00:52 Sharding - The problem
01:59 Horizontal Partitioning
03:20 Considerations
04:30 Potential Drawbacks
08:46 A challenge!
Video lectures, architecture diagrams, capacity planning, API contracts, and evaluation tests. It's a complete package.
Horizontal vs. Vertical partitioning: stackoverflow.com/questions/1...
Consistent Hashing:
en.wikipedia.org/wiki/Consist...
• What is CONSISTENT HAS...
Sources:
/ how-sharding-works
/ why-i-love-databases
www.quora.com/What-is-the-dif...
en.wikipedia.org/wiki/Partiti...)
Designing Data-Intensive Applications - amzn.to/2yQIrxH
#database #sharding #systemdesign
17 май 2024
