I have no experience in that field, but the isolation brought by a 1 customer <-> 1 DB relationship sounds VERY appealing to me. I'm talking about schemas, no d

I have no experience in that field, but the isolation brought by a 1 customer <-> 1 DB relationship sounds VERY appealing to me. I'm talking about schemas, no dedicated database servers. Creating dedicated database app users with the proper permissions pretty much guarantees that you'll never serve data to the wrong customer. It also probably makes bug and performance troubleshooting much easier. The biggest downside is probably the maintenance overhead, but I suppose automation can mitigate it quite well. It maybe makes internal reporting a bit harder, as you can't get the whole data from a single SQL query. You'd have to handle this in the application layer.