Q: What is project codename Astoria?
A: Astoria is a project in the Data Programmability team at Microsoft that explores how to provide infrastructure and tools for exposing and consuming data in the web. Astoria can create data services that are exposed in a natural way to the web, over HTTP and using URIs to refer to pieces of data; these data services can be consumed by AJAX front-ends, Silverlight-enabled web pages, desktop applications and more. At this time we’re making available two experimental elements of project Astoria: the Microsoft Codename Astoria toolkit and the Microsoft Codename Astoria online service. The “overview” document that is available at the Astoria web site provides a more complete introduction to Astoria.
Q: What is the difference between the Astoria CTP toolkit that is available for download and the Astoria online service?
A: The Astoria toolkit consists of a set of runtime components, documentation, samples and Visual Studio integration elements that allows developers to create and consume Astoria data services in their own ASP.NET web applications. The Astoria online service is an experimental deployment of the Astoria toolkit plus added infrastructure in the Microsoft Live Labs environment that can be accessed over the internet. The online service includes a number of pre-created sample data-sets exposed as data services, and soon it will offer the option of creating custom data services to allow for further experimentation with the technology using custom schemas and custom data.
Q: When will Astoria be available for deployment in production environments?
A: We are making this early prototype available publicly to gather feedback, understand customer needs and validate our assumptions about application scenarios. We will plan the rest of the release cycled based on that feedback. Currently there is not fixed schedule for releasing a production version of Asotira.
And also this:
One month trip from gloating to tears
Viridian has gone on the Redmond Diet with Microsoft today ripping some of its most exciting planned features out of the virtualization software.
In April, Microsoft's GM in charge of Viridian Mike Neil revealed that the company would have to delay the software's beta release from the first half of 2007 to the second half. The reason for the delay? Well, Microsoft wanted to add in things such as support for 64 processors – "something no other vendor's product supports" – and on-the-fly addition of processors, memory, disk and networking. Such technology was needed so that Microsoft could "(meet) our internal goals for performance and scalability."
... connect those dots maybe with a tourniquet. There's more at the article and then this excerpt:
These issues have some analysts calling for blood.
"Microsoft has a fundamentally broken server virtualization strategy at this point," wrote Illuminata analyst Gordon Haff. "They were behind to begin with. Now, the tardy 'Rev. 1.0' is starting to look more like 'Rev. 0.5.' Perhaps it’s time for Microsoft to consider a different angle.
"Perhaps it’s time for Microsoft to admit that they can’t do it all themselves - at least for now - and form some legitimate partnerships. That would mean fixing some licensing problems and eating some crow. But that’s the cost of a broken internal development process. That Mike Neil should make reference to the 'mythical man-month' in his posting is wholly appropriate." ®4 comments posted — Post a new comment