The State of Windows Azure
Description
Ever wonder how some applications are built? Ever wonder how to combine components of the Windows Azure platform? Stop wondering and learn how we've built MyGet.org, a multi-tenant software-as-a-service. In this session we'll discuss architecture, commands, events, access control, multi tenancy and how to mix and match those things together. Learn about the growing pains and misconceptions we had on the Windows Azure platform. The result just may be a reliable, cost-effective solution that scales.
Day:
1Share
Download
Download this episode
- MP3 (58.5 MB)
- Low Quality MP4 (345.1 MB)
- High Quality MP4 (757.9 MB)
- Mid Quality MP4 (529.0 MB)
Event Homepage
More episodes in this series
Big Data for the Win!!
Related episodes
What is going on? Tips and tricks around application diagnostics on Azure
Baantjer en de moord op de grote webservice
Reducing latency on the web with the Azure CDN
Reducing latency on the web with the Windows Azure CDN
How we Made MyGet.org on Windows Azure
Windows Azure Web Sites - Things They Don't Teach Kids in School
Patterns and Practices for Running Large Multi-Tenant SaaS Service on Windows Azure (How…
OAuth-as-a-service using ASP.NET Web API and Windows Azure Access Control
Brewing Beer with Windows Azure
SignalR. Code, not toothpaste.
The Discussion
-
KeyboardG This was a great talk. If you had to build the app on non-Azure hardware (maybe even on prem at a large enterprise even) what would have chosen for your message queues?