What do you think?

[barski]

Over the past year I've wrestled with various ways of dealing with datasets

and the whole "n tier idea".

 

I ran across this article a couple of weeks ago and I really like what the author has done. I was just wondering what some of the more experienced people on the board think?

 

http://www.microsoft.com/belux/nl/msdn/community/columns/hyatt/ntier1.mspx

 

PS this is a 4 part article and only 3 parts have been published

[Derek Stone]

The author hasn't "done" anything except rehash the largest software design pattern used in the last ten years.

[barski]

really. I've never seen an example of an implementation of the business layer like the one in his sample. But since it's that old then it must be ok to use. thanks

[donnacha]

This is such an old philosophy, the pictures make it look new.

[barski]

Are you guys reading parts 2 & 3 spefically part 2?

 

http://www.microsoft.com/belux/nl/msdn/community/columns/hyatt/ntier2.mspx

 

http://www.microsoft.com/belux/nl/msdn/community/columns/hyatt/ntier3.mspx

[PlausiblyDamp]

The articles seem to give a good explanation of what n-tier architectures are and some good methods of implementing them with .Net. I'm not sure the authors is doing anything other than trying to explain the concepts - nowhere did he seem to be taking credit for inventing this approach himself.

They seemed a good read and n-tier as several well known benefits and should generally be considered an option over the more traditional client / server model IMHO.