Astoria and Jasper are two projects to follow for building data driven applications of the future.
First one has codename "Astoria" and it's goal is
to enable applications to expose data as a data service that can be consumed by web clients within a corporate network and across the internet. The data service is reachable over HTTP, and URIs are used to identify the various pieces of information available through the service. Interactions with the data service happens in terms of HTTP verbs such as GET, POST, PUT and DELETE, and the data exchanged in those interactions is represented in simple formats such as XML and JSON.
The first early release of Astoria will be a Community Tech Preview that you can download, as well as an experimental online service you can access over the internet.
Check out the Astoria webpage at http://astoria.mslivelabs.com for more information and a link to the download.
Second one is called "Jasper" and aim at faciliating data-driven development. Developing data-driven applications could be tedios taks as developers have to spend a lot of time developing supporting infrastructure and Data Access Layer insead of focusing on real business problem. There are many O/R Mapping tools that reduce ammount of work by offering DB-classes mapping along with code generation. I personally though MS try to catch up with LINQ to SQL ( a.k.a DLINQ) and Entity Model in Visual Studio Orcas... but it sounds like they aim higher and use Entity Model for:
- Dynamic generation of data classes so there is no configuration or design time code-gen to carry around.
- Rich query and O/R capabilities because “Jasper” is built on top of the Entity Framework.
- Auto-binding capabilities for ASP.NET, WinForms, and WPF to make binding data to a UI simple and automatic.
Learn more about “Jasper” on the MSDN Data Access Incubation Projects site