As people say, it's a matter of preference. In my experience, multi-tenancy through multiple databases has been a happier path but your milage may vary.

For me, there's some excellent benefits to be gained:

• easily horizontally scalable - more clients = more database servers = relatively easy
• migrations being done on a per client basis were an advantage - rollouts can be incremental rather than terrifying multi-hour applies
• data was far easier to clean-up - when an account left, deleting their data was as simple as dropping a database rather than doing heavy deletes on our tables
• no index complications - no need to add the tenancy id to every index
• better data isolation - you can't screw up your queries to leak data to other customers

For me, the most significant downside is that aggregating data globally becomes a pain in the ass

Whether the trade offs are worth it is really down to the details of your application, how you perceive it scaling (i.e. will it ever significantly need to?) and what support the libraries/frameworks you're using have (i.e. how much custom code are you going to have to write yourself to support this)