database sharding strategy for a growing social app

were seeing some serious growth on our social app and our single database instance is starting to feel the strain. were considering sharding but im torn between horizontal and vertical sharding. for a social app, where user data can grow exponentially, whats your preferred approach? are there specific key designs youd recommend to avoid hot spots down the line? looking for real-world experiences here.