This is interesting in that it seems to organize tenants into their own database. I've built a few SaaS products with on the order of a few thousand customers

This is interesting in that it seems to organize tenants into their own database. I've built a few SaaS products with on the order of a few thousand customers per application. Performance can sometimes be a problem when each customer can have millions of rows but no relation between those customers. I believe this is pretty typical. What's the purpose of mixing different customer rows? You rarely aggregate them all together. A million rows is easy for a database but when there are billions together, it starts requiring deeper optimizations. The idea of each getting their own separate database makes intuitive sense to me but most tools for dB access aren't built with this in mind.