database sharding strategy for high-traffic apps

Things are really picking up with user activity, and our single big database is starting to slow us down. We're thinking about sharding it to spread out the work. What ways of sharding have worked well for you? Are you doing it horizontally, vertically, or a mix of both? Got any advice on picking the best shard key and handling queries across shards without tanking performance?