I am looking into creating a Azure Mobile Service project and I also want to send push notifications to iOS and Android apps (Xamarin).
I don't have an Azure account and I am wondering if there is an easy way to self host the Azure Mobile Service project and use all its functionality?! Or do I have to host it on the Azure servers?
Thanks for you help!
Azure Mobile Services uses Notification Hubs for push, which is an Azure service that requires a subscription.
Related
I am creating my website application in .net core 2.1. I have to deploy it in WebApp of Azure.
I am bit new to WebApp so not sure if I need to enable any service or any port on WebApp so Notfication works.
Otherwise normal way to show Notification is SignalR implemented.
1) Will SignalR will work for website hosted in WebApp?
If any Azure service that will do same please suggest
SignalR uses web sockets to connect with clients, so you will need to go into app settings and enable them for SignalR to work.
Here is a tutorial to help you set up your WebApp with SignalR:
https://learn.microsoft.com/en-us/aspnet/core/signalr/publish-to-azure-web-app?view=aspnetcore-2.2
Based on your scenario, Azure SignalR Service or Azure Notification Hub may be an option for you.
There is notification service in Azure Web Apps around sending push notification to Mobile Devices that are integrated with Azure.
In your case i assume you are talking about sending real time notifications within the web app ? Yes SignalR works great for that scenario , and you can look into dedicated SignalR service from Azure for this.
https://azure.microsoft.com/en-au/services/signalr-service/
I am doing mobile development on Xcode and using hosted database from Microsoft Azure.
I noticed there is firewall settings on Microsoft Azure in order to add clients.
How will this work when the mobile app is deployed? Should all ports be opened on the database? Or do I need to use Web Services?
How will this work when the mobile app is deployed? Should all ports
be opened on the database? Or do I need to use Web Services?
You should definitely NOT open all ports and direct connectivity to the database from mobile apps is strongly discouraged.
Recommended way would be to use some kind of service layer sitting between your mobile app and the database. All the requests from the app should go to this service layer which will perform database operations. This service layer could be deployed as Azure Mobile App Service, Azure API App Service or a Web API hosted in Azure Web Apps Service.
I'm planning to use Web Apps feature of Azure App Service and separate the front-end app from one for back-office app. Can I use Service Bus in Azure App Service?
Or Is that something not required.I'm just implementing this design:
https://azure.microsoft.com/en-us/solutions/architecture/medium-umbraco-web-app/
Yes, you can use Azure Service Bus in Azure App Service.
We got caught by Microsoft's abandonment of Silverlight and focus on UWP. This has ended up with us having to develop two dually focused apps (UWP and Silverlight), which has left us with two apps that cannot be bundled/packed together. We have therefore decided to have of the apps as a companion app.
Both apps use authentication, at present time it is with Microsoft authentication. The services used for authentication is of the type Azure App Service - Mobile. The services besides authentication also provides interfaces to a notification hub, blob storage and SQL storage.
The question is therefore is it possible to have one App Service - Mobile (not mobileservice), and authenticate two different apps using the same service?
Additionally can the same Notification Hub be used to send notifications towards different apps?
Or is it needed that we create two different services for each application to facilitate the use of authentication and push messages. Then we can link the same database to the two App Service - Mobile ? But this would leave the issue of the notification hubs not having the same registrations ?
I dont think you can have more than one apps connected to one Azure mobile app. You can connect same app on different platforms but not multiple applications for same platform as Mobile app is designed to be an individual app back end.
Check this feedback request.
https://feedback.azure.com/forums/218849-notification-hubs/suggestions/3821272-push-notifications-for-multiple-apps
As answered by product group, the idea behind Mobile App is to be the individual backend. For that, Mobile Apps dashboard should have not one field for the PackageId/..., but two or more to be the backend for a different apps. Every connection between app and external service like a authentication provider or push notification platform is "personalized" - by IDs and password or certificates, or many ways.
I can imagine the scenario when someone would need to connect one backend to different apps, but the Azure Mobile App idea is different. And, as App Service is a service, i think that in the current situation what you want to do is impossible.
an Azure Mobile App consists of the client app and a backend in Azure. There's no stopping you reusing the same backend for more than one app.
I have an azure mobile service that is running on top of SQLAzure DB. The Database is geo-replicated. I am looking to setup a failover for mobile service in case if the primary endpoint goes down. I have looked into traffic manager but it does not support mobile service endpoints also setting up another mobile service that talks to the replicated DB not possible as the replicated copy is read-only.
What are the possibilities of setting up a failover for mobile services endpoints.
There are several mechanisms for hosting mobile APIs on Azure - Azure Mobile Services is tied to a single region, so you can't fail that over. Azure Mobile Apps is the next generation of Azure Mobile Services and is built on top of Azure App Service Web Apps - it's an extension of the work there. As a result, you can leverage all the cool features of Azure App Service for your mobile service. If you haven't taken a look yet, then take a look at migrating your service to Azure App Service Web Apps.
Once there, Traffic Manager is definitely what you want. You can read about the process of using Traffic Manager with an Azure web app here: http://blogs.msdn.com/b/benjaminperkins/archive/2014/06/02/using-traffic-manager-with-microsoft-azure-web-site.aspx