Database Sharding Strategy: Which Approach Do You Prefer?

Hey everyone, I'm trying to figure out the best way to shard a database for an app that's getting pretty big. We have tons of data, and our current setup just can't handle it. I've been looking at key-based sharding and range-based sharding. Both have their good and bad points, you know? Key-based could spread things out nicely, but I'm worried about how to handle queries that need data from different shards. Range-based looks easier if our data is ordered, but I'm concerned about hitting one shard too hard, making it a bottleneck. I'd love to hear what you all have tried and what worked for you. Did you find any specific tools or methods especially helpful?