InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

WinFS Officially Dropped

Posted by Rafael Ferreira, Floyd Marinescu on Jun 26, 2006

Sections
Architecture & Design,
Development,
Operations & Infrastructure
Topics
.NET ,
Data Access
Tags
Microsoft ,
Windows Vista
On the WinFS team blog on Friday, Quentin Clark blogged that WinFS, the new relational filestore would no longer be shipped as a separate product, instead, parts of it will make it into other projects:

 - "...in the next version of ADO.NET for Orcas...the Entities features we are now building in ADO.NET started as things we were building for the WinFS API."
 - "We are choosing now to take the unstructured data support and auto-admin work and deliver it in the next release of MS SQL Server, codenamed Katmai."

The announcement is being perceived as positive spin on the obviously negative fact that WinFS is dead.  One commenter on Quentin's blog said it quite bluntly:
Ok, so you were able to salvage some of the years' worth of work put into WinFS and apply it to other platforms.  But in this posting you are severely twisting what WinFS was.  WinFS was *not* a platform for developers building on SQL Server, it was a part of Windows.  Heck, it was even billed as an entire "pillar" of the (at-the-time) Longhorn OS.
WinFS was infact billed as one of the three pillars of Vista, along with Avalon and Indigo.   On the impact of this news on .NET development, Alex James writes:
Sure we will have ADO.NET Entities and SQL server will have more features, but at the end of the day there will be no relational file system:

    * We won't be able to run SQL like queries against the file system.
    * We won't be able to bridge other data into the file system.
    * We won't be able to bridge structured databases and unstructured files/emails.
    * We won't have a framework for promoting meta-data from proprietary file formats.
    * We won't have a file system with cool replication technology.

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.