Database Application level sharding is the process of splitting a table into multiple database instances in order to distribute the load. However, Sharding a database is an expensive operation (maintainability and overhead) and I suggest you do that only when you absolutely need to. That means when your single instance database can no longer serve queries with minimum latency. So I suggest you monitor that and only shard if necessary.. I rather do replication make master / backup and make requests read from replica than Sharding just because it is easier.. good question... nice idea for a video Time codes 0:00 Intro 5:00 Partition horizontally 7:45 Replication (Master/backup) Scale reads 11:00 Scale writes by region 12:30 Sharding 16:40 Sharding in YouTube 🏭 Software Architecture Videos    • Software Architecture   💾 Database Engineering Videos    • Database Engineering   🛰 Network Engineering Videos    • Network Engineering   🏰 Load Balancing and Proxies Videos    • Proxies   🐘 Postgres Videos    • PostgresSQL   🚢Docker    • Docker   🧮 Programming Pattern Videos    • Programming Patterns   🛡 Web Security Videos    • Web Security   🦠 HTTP Videos    • HTTP   🐍 Python Videos    • Python by Example   🔆 Javascript Videos    • Javascript by Example   👾Discord Server https://discord.gg/CsFbFce Support me on PayPal https://bit.ly/33ENps4 Become a Patreon https://www.patreon.com/join/hnasr Stay Awesome, Hussein