As applications grow, the number of application users and the amount of data it stores increase over time. If the data volume is too large or too many users attempt to use the app, application performance and customer experience radically degrade.
Database sharding is one of the best methods to solve this problem. Or is it?
- Sharding adds complexity.
- Sharded databases can lose ACID compliance.
- Sharding can negatively affect database performance and reliability.
- Sharding is manual, requiring more resources to implement.
In this webinar, Brian Walters, Solution Engineering at PingCAP, breaks down the major sharding challenges facing developers and architects. He’ll then explore how one can avoid those challenges with a distributed SQL database.