Windows Azure Mobile Services:
- Accelerate your mobile app development. Incorporate structured storage in the cloud, user authentication(Facebook, Google, Microsoft, Twitter, Active Directory account)/authorization and push notifications to millions (Notification Hubs) in minutes. Add your custom backend logic in C# or Node.js
- Introduction to Azure Mobile Service – Scott Guthrie
Below are some tutorials that walkthrough common authentication/authorization/push scenarios you can do with Windows Azure Mobile Services:
- Create a self-signed Management Certificate. Open a Visual Studio command prompt(As administrator). Details.
makecert -sky exchange -r -n "CN=AzureCertificateName01" -pe -a sha1 -len 2048 -ss My "AzureCertificateName01.cer"
- Upload Management Certificate to Azure
To upload a management certificate to Windows Azure, go to the Settings page in the Management Portal, and then click MANAGEMENT CERTIFICATES.
- To install Windows Azure PowerShell. Download here.
- Set Windows PowerShell execution policy (As adminstrator):
PS C:\> Set-ExecutionPolicy RemoteSigned
- Store Azure Subscription and Certificate locally (Run once) details.
$mySubID = "subscritionID"
$certThumbprint = "Thumbprint"
$myCert = Get-Item cert:\CurrentUser\My\$certThumbprint
$mySubName = "SubscriptionName"
Set-AzureSubscription -SubscriptionName $mySubName -Certificate $myCert -SubscriptionID $mySubID
- Select Azure Subscription
Select-AzureSubscription -SubscriptionName $mySubName
- Store Azure Subscription and Certificate locally
Start-AzureVM -ServiceName "myCloudServiceName" -Name "myVMServiceName"
Stop-AzureVM -ServiceName "myCloudServiceName" -Name "myVMServiceName"
The scenarios covered include creating topics and subscriptions, creating subscription filters, sending messages to a topic, receiving messages from a subscription, and deleting topics and subscriptions.
After your web site project has been pushed to a repository web site, in the Windows Azure Portal quick glance section, select Set up deployment from source control. The Set Up Deployment dialogappears that asks Where is your source code?.
Choose the source control method that you are using.
When prompted, enter your credentials for the service you selected.
After you have authorized Windows Azure to access your account, you will be prompted with a list of repositories.
Select the repository that you want to associate with your Windows Azure web site. Click the checkmark to continue.
When enabling continuous deployment with GitHub or BitBucket, both public and private projects will be displayed.
Windows Azure will create an association with the selected repository, and will pull in the files from the master branch. After this process completes, the deployment history on the Deployments page will show an Active Deployment message like the following:
At this point your project has been deployed from your repository of choice to your Windows Azure web site. To verify that the site is active, click the Browse link at the bottom of the portal. The browser should navigate to the web site.
To verify that continuous deployment is occurring, make a change to your project and then push the update to the repository you have associated with this web site. Your web site should update to reflect the changes shortly after the push to the repository completes. You can verify that it has pulled in the update on the Deployments page of your Web Site.
How continuous deployment works
Continuous deployment works by providing the DEPLOYMENT TRIGGER URL found in the deploymentssection of your site’s Configure tab.
When updates are made to your repository, a POST request is sent to this URL, which notifies your Windows Azure Web Site that the repository has been updated. At this point it retrieves the update and deploys it to your web site.
Specifying the branch to use
When you enable continuous deployment, it will default to the master branch of the repository. If you want to use a different branch, perform the following steps:
In the portal, select your web site and then select CONFIGURE.
In the deployments section of the page, enter the branch you wish to use in the BRANCH TO DEPLOYfield, and then hit enter. Finally, click SAVE.
Windows Azure should immediately begin updating based on changes to the new branch.
You will learn how to
- Configure the Application to Use Service Bus
- How to Create a Queue
- How to Send Messages to a Queue
- How to Receive Messages from a Queue
- How to Handle Application Crashes and Unreadable Messages
Now that you’ve learned the basics of Service Bus queues, follow these links to learn more.
The Windows Azure Service Bus provides two comprehensive messaging solutions – one, through a centralized “relay” service running in the cloud that supports a variety of different transport protocols and Web services standards, including SOAP, WS-*, and REST. The client does not need a direct connection to the on-premises service nor does it need to know where the service resides, and the on-premises service does not need any inbound ports open on the firewall.
The second messaging solution, new in the latest release of the Service Bus, enables “brokered” messaging capabilities. These can be thought of as asynchronous, or decoupled messaging features that support publish-subscribe, temporal decoupling, and load balancing scenarios using the Service Bus messaging infrastructure. Decoupled communication has many advantages; for example, clients and servers can connect as needed and perform their operations in an asynchronous fashion.
A common use-case for a web site is to collect data for storage in a database in an enterprise environment. Likewise, the first thing most customers want to move into the cloud is their web site. Ironically, the idea of moving a whole enterprise architecture into the cloud can appear to be a daunting task. So, if one wants to host their site in the cloud but keep their data in their enterprise, what’s the solution? This post will address that question and point out how the Windows Azure Service Bus between a Windows Azure Web Site and an on-premises database can be a great glue between your web site and your enterprise.
This article analyzes the differences and similarities between the two types of queues offered by Windows Azure today: Windows Azure Queues and Windows Azure Service Bus Queues. By using this information, you can compare and contrast the respective technologies and be able to make a more informed decision about which solution best meets your needs.
Windows Azure supports two types of queue mechanisms: Azure Queues Storage and Azure Service Bus Queues.
Windows Azure Queues, which are part of the Windows Azure storage infrastructure, feature a simple REST-based Get/Put/Peek interface, providing reliable, persistent messaging within and between services.
Service Bus Queues are part of a broader Windows Azure messaging infrastructure that supports queuing as well as publish/subscribe, Web service remoting, and integration patterns.
While both queuing technologies exist concurrently, Windows Azure Queues were introduced first, as a dedicated queue storage mechanism built on top of the Windows Azure storage services. Service Bus Queues, introduced with the latest release of the Service Bus, are built on top of the broader “brokered messaging” infrastructure designed to integrate applications or application components that may span multiple communication protocols, data contracts, trust domains, and/or network environments.
This article compares the two queue technologies offered by Windows Azure by discussing the differences in the behavior and implementation of the features provided by each. The article also provides guidance for choosing which features might best suit your application development needs.
- ✔ Manage all your Windows Azure blobs in one place
- ✔ Reliably upload and download blobs with a responsive UI
- ✔ Transfer blobs between your storage accounts
- ✔ Easily search and filter your blobs
This guide will show you how to perform common scenarios using the Windows Azure Queue storage service. The samples are written in C# code and use the Windows Azure Storage Client for .NET (Version 2.0). The scenarios covered include inserting, peeking, getting, and deleting queue messages, as well ascreating and deleting queues. For more information on queues, refer to the Next steps section.
Table of contents