Data Driver

Blog archive

Azure Mobile Services Now Support Blob, Table Storage Options

Microsoft yesterday announced enhancements to its cloud-based backend for mobile apps, including new data storage options.

Windows Azure Mobile Services (WAMS), a preview announced in late August, provides data storage and other services to developers without the time, talent or inclination to wire up the server-side code themselves. Previously, data access was available through simple management-portal-created SQL Databases, or, as I detailed earlier, an existing database.

Now, WAMS also provides support for Windows Azure Blob and Table storage, Microsoft's Scott Guthrie announced yesterday. "This is supported using the existing 'azure' module within the Windows Azure SDK for Node.js," Guthrie said. He provided an example to show how easy it is to use the new support for Tables:

The below code could be used in a Mobile Service script to obtain a reference to a Windows Azure Table (after which you could query it or insert data into it):

var azure = require('azure'); var tableService =
   azure.createTableService("< account="" name="">>", "< access="" key="">>");

Guthrie pointed to the Windows Azure Node.js dev center for tutorials on using the new data storage options via the "azure" module.

Other services were also announced as Microsoft continues to flesh out its preview offering, including support for iOS apps through the use of native iOS libraries. Previously, only Windows 8 apps were officially supported, though Microsoft partner Xamarin developed an open source SDK for MonoTouch for iOS and Mono for Android, available on GitHub, which also hosts the open source WAMS SDKs and samples.)

One reader expressed surprise that iOS support was added before Windows Phone, the most obvious choice of client to use WAMS. "Holy crap," said the reader. "iOS before Windows Phone? Come on guys. The WP7/8 OS is legit. Give it first rate support with your own products."

As the iOS support reflects a nod toward the ubiquity of Apple mobile devices, other enhancements reflect the pervading need for the requisite "social" services in modern apps. These include support for Facebook, Google and Twitter authentication and the ability to send e-mails and SMS messages from WAMs apps. Also, server deployment to the West region was added (previously only the East region was available).

As WAMS continues to evolve, with Windows Phone support probably coming soon, so does the entire Windows Azure ecosystem. "We'll have even more new features and enhancements coming later this week--including .NET 4.5 support for Windows Azure Web Sites," Guthrie said. "Keep an eye out on my blog for details as new features become available."

What do you think of the new data storage options available in the do-it-yourself cloud backend for mobile apps? Comment here or drop me a line.

Posted by David Ramel on 10/17/2012


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube