Okay, here's the deal, I created an App that is basically just a wrapper that has several links that launch multiple web sites. No big deal, but now, the requirements have changed. They want this one app to handle log in functionality, pass credentials, and handle push notifications to the phone/tablet from these multiple sites.
These other sites reside on an Azure server where each site has it's own database. They are ASP.NET/SQLServer Express backend. We added HTML5 controls to the UI so they look/feel like a native phone/tablet app. It's roughly 5 different ASP.NET/HTML5 websites with 5 different cloud SQLServer DB's.
Our thinking is to have a separate DB for the Appery App. It would contain the LogIn/Authentication table and check/pass along credentials to the other websites. Then it would also contain an Alerts table that the other sites would write to. When this table is populated, and it's for a particular user, the alert is Pushed to their device.
Should I write a REST service and implement all this in an SQL DB on Azure? Should I use an Appery DB and pass data back/forth from Azure?
Should I use the Appery DB Users/Device collections or create my own?
Etc, etc? I'm looking for any and all suggestions. I've written a few REST services and am new to NoSQL (MangoDB/DocumentDB)
What's the best way to go about this? We want this to run on Android and iPhone so we'll use both their notification services but trying to keep the App as close to HTML5/css phone-gap app to work on multiple devices.
Thanks!