It's all great, but there is no "Express" version for VS Online Basic to match the free desktop Express IDE. The Pro version is introduced at $22/mth, and that's headed to $45/mth. The cost of using this IDE will be $540 per year. That's a high hurdle for poor devs, students, and new programmers. I wish you would add code analysis and other desktop Pro features to this IDE, leave the Pro price in place to cover those features, and make the current Monaco IDE the "Express" version for VS Online Basic accounts and sell it for something like $10/month. I want to use Monaco, but there is no way that I'm going to spend $540/year for it ... ever!
But where is the "Express" version of the IDE for the Basic VS Online? Currently, VS Online Basic is inappropriately named because there is no Basic VS IDE. All you get with VS Online Basic is some source control, team tools, and build time. Without an Express-level IDE, it really isn't "Visual Studio," is it??
Introductory pricing on VS Online Pro is $22/month and headed to $45/month ... TOO expensive for small one-person shops. There should be an "Express" version IDE that mirrors the feature set of desktop "Express" VS. Think about that cost under GA pricing: $540 per year ... and the desktop IDE is around $500. That's not good, especially for a "lightweight" version of the IDE.
Also, when you say "lightweight" IDE ... what does that mean? None of the docs in Azure, at the VS website, or in the video here explain exactly what is left out of desktop Pro IDE. Are we supposed to guess what was left out?
Still wish we could go back (officially) to calling it "SQL Azure" ... "Azure SQL Database" is too long ... to clunky ... sounds dumb. You can't say "SQL Database" all by itself, because that doesn't tell you anything. I still think you should have a chat with marketing about changing it back. "SQL Azure" and "SQL Server" ... quick, easy, right to the point, no minunderstandings. I'm going to be a rebel and keep calling it "SQL Azure."
Mark, thank you for this great presentation. I was confident in Azure before, but I'm even more confident following your talk that the Azure infrastructure is well-built and well-maintained. You answered many of my curiosities about how the datacenters function. I highly recommend watching your presentation to all current and future Azurites.
Disagree with both presenters on the point that the new caching structure is ALWAYS better. If an app is running just fine on two ExtraSmall instances ($29) with the AppFabric Caching Service at 128MB ($45), you are at about $74 per month. The new Azure Caching is only available for Small instances. Two Smalls will cost about $144 (6-month plan). That's $70 difference! ... per month! It's a world of difference in cost. In fact, you have to get all the way up to 7 ExtraSmall instances with 128MB AppFabic cache before you get to the cost of 2 Small instances.
If the app only needs a few ExtraSmall instances because it's a low demand app, but you still want the speed of a cache so that those on the app do have a better experience with it, then the AppFabric Cache is a GREAT solution. The new caching system wouldn't be a good choice under these conditions.
Also note that ExtraSmall instances have rather limited memory available. Because AppFabric caching service runs totally outside that memory, it's the perfect choice for those running things on ExtraSmall instances.
Therefore, I hope MS will keep the old AppFabric cache around. I sort of doubt it ... it might even be a marketing play to get many apps off of the el cheapo ExtraSmall instances. I have noted that the AppFabric system has been removed from the Azure pricing calculator. That seems to indicate that they are going to depreciate it at some point. My suggestion is to keep it around.
Just about the most USEFUL and HELPFUL presentations I've ever had from MS. Thanks for this Jai ... I learned a great deal, including some very important tips that I can build into my apps right now for faster and more reliable code! I especially appreciated the section on working with table storage, as I'm about to move at least a dozen tables from SQL Azure into table storage. Great Job! Thanks again.