The question is: what data sources should Astoria support as inputs? Should we allow ADO.NET Entity Framework only or open up more? If we open up more, how does the system need to be layered to enable the use of those alternate data sources?
Deciding on something that becomes a public interface of a developer-oriented technology is a tricky task. Not only does the resulting design need to be correct and complete, but also there are various aspects that are more around aesthetics and personal preference.
Some time ago we shipped Visual Studio 2008 Beta 2 and a couple of weeks later we added the ADO.NET Entity Framework Beta 2 release as well as the first CTP of the tools for it. Once all of the frameworks/tools were in Beta 2 we got a bunch of email “encouraging” us to release a Beta 2-compatible version of the Astoria CTP 🙂
The goal of Astoria is to make data available to loosely coupled systems for querying and manipulation. In order to do that we need to use protocols that define the interaction model between the producer and the consumer of that data,