This course teaches you how to manage application and network services in the Azure ecosystem.
By the end of this course, you'll have gained a firm understanding of the key components that comprise the Azure application and network services ecosystem. Ideally, you will achieve the following learning objectives:
- How to use Active Directory.
- How to understand networking strategies for Azure and communication services.
- How to use Redis cache.
This course is intended for individuals who wish to pursue the Azure 70-532 certification.
You should have work experience with Azure and general cloud computing knowledge.
This Course Includes
- 1 hour and 10 minutes of high-definition video.
- Expert-led instruction and exploration of important concepts surrounding Azure application and network services.
What You Will Learn
- How to utilize Azure Active Directory.
- How to implement Azure communication strategies.
- How to take advantage of Redis caching.
Hello and welcome back. We'll now start to take a look at Notification Hubs, the last topic for this section.
Azure Notification Hubs provide an easy to use service that allows you to send push notifications from your app to any supported mobile platform such as Windows phones, Android phones, iPhones or even a Kindle e-reader. Applications can easily send cross-platform push notifications to various platform notification systems without having to worry about low level details.
Notification Hubs allow for pushing high scale volumes of low latency messages to millions of recipients. A typical use case might be sending an informational update to all the clients of your multiplatform mobile app. Another example may be sending a time-sensitive one-time password for multifactor authentication to a client without having to worry about the platform specifics of that client and knowing that the message will arrive in a timely manner.
Push notifications are enabled through platform specific platform notification systems known as PNSs. This means that sending a push notification to an Android or iPhone or Windows phone client, for example, requires you to talk to the specific PNS for that platform. It's where the Notification Hub provides a useful abstraction. It's worth being familiar with the currently supported notification platforms, which currently include Microsoft, Apple, Google, as well as Amazon, and Baidu.
Let's go to the Azure portal now and see how we can set up a Notification Hub. I'm here in a classic portal and as our final exercise in this section let's create a Notification Hub. We click New at the bottom. And then from here we can click Notification Hub and Quick Create. Let's give it a name, so Test NH. Having created our Notification Hub, we see here the familiar dashboard with key statistics about the status of our Hub service. If we click on the Configure tab, the Configure tab allows us to specify our credentials when communicating with the various platform services. At the bottom we see the familiar section with shared access policies and shared access keys.
This section has covered a variety of topics related to implementing a communication strategy. We discussed and created a Service Bus namespace. We looked at Relays and how they enable us to expose on-premises services. We covered Queues, Topics and subscriptions, and related messaging strategies. And lastly, we discussed the topics of Event Hubs and Notification Hubs.
In the next section we'll look at scaling Service Bus, which will recap some of the points we've discussed so far.
Isaac has been using Microsoft Azure for several years now, working across the various aspects of the service for a variety of customers and systems. He’s a Microsoft MVP and a Microsoft Azure Insider, as well as a proponent of functional programming, in particular F#. As a software developer by trade, he’s a big fan of platform services that allow developers to focus on delivering business value.