This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Yukon is a platform
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
After much avid reading on Yukon/SQL 2005, I've reached some conclusions about it. Take a look at Tiago's post "Is Yukon the end of the middle tier ?" for a thorough discussion of Yukon's place in the architectural universe.
It's taken me quite some time to get to this, but Yukon will be a platform. Just like Windows. The recent addition of Reporting Services to SQL 2000 just makes this more apparent. I mean, we've already got SQL mail, and sql xml. With the CLR inside, there will be absolutely no reason to develop inside the DB. Develop as in actually developing an entire app.
The group that will first start using Yukon as a platform will be those most comfortable in the DB in the first place - DBAs. Obviously, those that fall into Tiago's second group will follow suit.
I believe that this will work great for certain types of apps, and, if there will be an MSDE sized Yukon, then many apps could go this route. However, once you leave the "app" size/context and move to that of the "system" then the DB can't be the system, by definition.
I'm worried that some of the enthusiasm of developing apps in Yukon will drive people to start developing systems in it. I guess that it's clear that I fall into Tiago's first group of developers :) This is most probably colored by the size of systems I'm acustomed to developing.
What do you think ? Will Yukon become the next platform for app development - similar to Access ( similar - as in, not the same ) but at a higher level ? Would it be suitable for systems development ? Let me know - prove me wrong :)
Previous Topic
