Microsoft DevRadio: (Part 1) Using Windows Azure to Build Back-End Services for Windows 8 Apps
- Posted: Feb 06, 2013 at 4:00AM
- 3 comments
Like what you heard? Try Windows Azure for FREE and enjoy the freedom to use your preferred OS, language, database or tool. Windows Azure can help you deploy sites to a highly scalable environment, deploy and run virtual machines, and create highly scalable application in a rich PaaS environment. Give it a try!
_________________
Abstract:
Peter Laudati and Brian Hitney welcome fellow Developer Evangelist, Andrew Duthie to the show as they kick off their series on how to build back-end services for their Windows 8 apps using Windows Azure. Tune in for part 1 as Andrew gives an overview of the series and introduces some potential techniques you could incorporate as you build your back-end services.
After watching this video, follow these next steps:
Step #1 – Try Windows Azure: No cost. No obligation. 90-Day FREE trial.
Step #2 – Download the Tools for Windows 8 App Development
Step #3 – Start building your own Apps for Windows 8
Subscribe to our podcast via iTunes or RSS
If you're interested in learning more about the products or solutions discussed in this episode, click on any of the below links for free, in-depth information:
Register for our Windows Azure Hands-on Lab Online (HOLO) events today!
Blogs:
Videos:
- Microsoft DevRadio: How to Get Started with Windows Azure
- Microsoft DevRadio: (Part 1) What is Windows Azure Web Sites?
- Microsoft DevRadio: (Part 2) Windows Azure Web Sites Explained
Virtual Labs:
Comments closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.
More entries in this blog
-
Microsoft DevRadio: Integrating Microsoft…
-
Microsoft DevRadio: (Part 1) Using Windows Azure…
-
Microsoft DevRadio: (Part 10) Practical Azure with…
Follow the discussion
Oops, something didn't work.
What does this mean?
Subscriptions allow us send you email notifications when new content is added. You need to be signed in to Channel 9 to use this feature.What does this mean?
Subscriptions allow us send you email notifications when new content is added.sign up for email notifications?
Azure backend is great, but here is a million-dollar question: which Win8/WP8 payment model does actually support Azure costs which are in their nature per-usage?
Neither a subscription-based payment model nor in-app feature purchases can address the issue of per-usage costs. Why isn't there a pay-as-you-go model that would allow users to purchase some sort of credits, which would then offset Azure traffic/storage costs?
As it stands, there's no point in building WP8/Store applications with Azure backend because it is financially unsustainable business model.
vkdev,
Actually, with the exception of Azure Compute, most of the services I discuss in the series are either free or charged on a monthly basis.
I do use the Azure SQL Database, which is charged monthly, for data storage. The same SQL Database, however, can be used across multiple services.
Windows Azure Mobile Services and Windows Azure Web Sites (the latter is what I use for the ASP.NET Web API version of my back-end service) are both available as free offerings in shared mode, so assuming you used the Azure SQL Database offering for the data storage, your cost would only be $10/mo.
You can find pricing details for Mobile Services and Web Sites at:
http://www.windowsazure.com/en-us/pricing/details/#data-management/
Hope that helps!
Thanks for the info.
I'd say that the choice of the payment model has to be figured out very early in the development because it greatly affects the overall cloud application architecture.
Even if one starts with free services and/or by paying (I assume you meant fixed) Azure costs on a monthly basis, scaling up (which is why Azure is the choice for the back-end) will inevitably push people towards shared or reserved instances and, essentially, pay-as-you-go costs.
By the time one realizes that the scaling up implies switching to a different payment/business model because the costs are, after all, per-usage and not fixed nor regular, it will be too costly (or even too late) to go back and try to retrofit into the application architecture a different payment model in order to offset those costs.
In fact, at the moment there does not seem to exist such a model which would match pay-as-you-go on the back-end side.
Speaking of which, I just started looking at the WP8's Wallet functionallity, specifically OnlinePaymentInstrument. Perhaps that can be used as a way to maintain some sort of a user account balance, which can increased with occasional payments (i.e. pay-as-you-go).
The trouble is, there is no equivalent functionality on Win8, but that's a problem for another day.
Remove this comment
Remove this thread
Close