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
- Manual sharding can lead to unbalanced shards and hotspots and must be manually rebalanced
- Sharding affects the ability to do aggregations across shards
- New application features may require re-sharding and database migrations
- Applications require sharding logic for distributing and retrieving data
- Joining data from multiple shards requires multiple queries
- MySQL has no native support for sharding
In this webinar, Brian Walters, Solution Engineering at PingCAP, breaks down the major sharding pitfalls facing developers and architects. He’ll then explore how one can avoid those pitfalls with a distributed SQL database.
Join us Tuesday, April 25th to learn how a distributed SQL architecture works to remove the burden of database sharding and free up developer productivity and business innovation.