For my web application with a postgresql backend I'm now looking into schema's. As I switched from MySQL to Postgresql(because of (amongst others) the proper geospatial extension) I was not aware of the concept of schemas.
In my application every customer now has his own database with tables and off course content. The user management and authentication is done with an 'oversight' database. This makes it possible for one user to have access to several DB's (several customers, ideally for administration purposes).
customer1, customer2,....., oversight
The structure of DB1 is not necessarily the same as DB2. In fact it even can be a complete different 'application'.
For now there is absolutely no interaction between the two databases; but in the future I want to collect statistics (read-only) from the several databases.
Does it have more advantages to use schema's instead of separate databases with properly setup roles? Or is it better to use the different-database-setups.