My general feeling is that this is a question which must have been answered but I am struggling to find resources for it. I know little about mobile app dev but my knowledge of web services is pretty good.We are looking to expand our existing software suite to include a mobile app. Each client has the software and databases installed on their own servers. The actual data is very client specific. The services will be developed internally & the app itself outsourced. Basically what needs to happen is:We need to create web services hosted at each client to expose the information in the DB.The mobile app needs to connect to a service which gives it the correct info based on the user.New clients could buy into the app at any momentSo I've thought that we could possibly host a routing service, which means the app only connects to one service and it figures out where to go according to the user credentials. I think this could slow things down considerably, although it would be easier for the actual app dev. Since we own the service adding a new client would be easy.The alternative is for the app to be able to figure out where to go based on the company and credentials the user enters.Could I be missing other alternatives?Can anyone help with resources or advice around this problem?
Architecture: mobile apps for different clients with their own dbs different servers?
architecture;database;rest;mobile;wcf