:) haa haaa SORRY I forgot to mention the whole server instance part and my answer seems out of sync with the question! I think it's not much different from one database for one tenant. But maintenance would be a big headache (again it depends on your resources and requirement). You have to consider things like:
Interesting... with either of them there are pros and cons, and I would recommend you to read this discussion.
I have implemented 'A shared database, shared schema' with the flexibility to isolate on demand based on selected plan.
DATABASE_1
tenants
tenant_users
DATABASE_2 (just an example)
app_users
app_countries
Thanks for this example and link. I feel like there's a lot of sides and each has their merit... probably not a "wrong" answer
:) haa haaa SORRY I forgot to mention the whole server instance part and my answer seems out of sync with the question! I think it's not much different from one database for one tenant. But maintenance would be a big headache (again it depends on your resources and requirement). You have to consider things like:
Yeah that's the kind of stuff I was thinking about as well: the peripheral things for the application. Great point