I’m tweaking our database infrastructure and thinking about sharding to manage our growing data sets. But I’m a bit worried about the performance hits we might take with complex queries. Does anyone know of any good alternatives to sharding that could help us scale out without sacrificing performance?
We experimented with horizontal sharding by distributing our data across multiple servers based on customer ID. Although it helped us manage load better, we’ve seen a significant increase in latency, especially during complex query operations that span multiple shards. We’ve tried optimizing our indexing strategies, but the latency issues persist
DB smith is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.