Jan 11, 2018 07:53 AM|XIII|LINK
it's not just the transactional part, what if you have a load of users on your service? You want to make money out of it so likely you want quite some users and scale out your SaaS solution.
What's the reason behind their question to be able to see/manipulate the data?
Another solution would be that you deploy your application on your server (for example on Azure Web App Services) and use one master database for all your configurations parts and internal stuff. Anything client related, their data, goes into another SQL
Database (also on Azure in the same data center otherwise the latency becomes too high) and connect to that depending on configuration you keep in your application. Make a tight contract with the client(s) that their database is their responsibility and if
something goes wrong it's their responsibiltiy. All you provide is the needed database scripts to set up their database so that your application can work with it. Otherwise make up a maintenance contract that you'll handle the upgrades etc and that they pay
a monthly flat fee for that. When a user of client X makes a request to your application you'll have to figure out in the application who it is and to which database it should go to grab the data.