Debate: Do We Really Need Three Layer Architecture?

home
ado.net
view story

22 Kicks

Debate: Do We Really Need Three Layer Architecture?(forums.asp.net)

submitted by joycsc(1597) 3 years, 6 months ago

How many of you changed your database vendor (i.e. Sql Server, Access) after developing an application? How many of your data entities include business logic? I could say, less than 10% in both cases for my case. I found the similar statistics for my other known developers. I guess this is true for less that 10% of the developers around the world.

7 comments |category: ADO.NET |Views: 750
Tweet

tags: ASP.NET ADO.NET Database another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

More who kicked this story...

Comments:

posted by cwbrandsma(1711) 3 years, 6 months ago 0

About 90% yes.

posted by codeguru(80) 3 years, 6 months ago 0

:D you gotta be kidding.

it is always a good practice to start with well known architecture for the future needs of the application.

posted by Jemm(9604) 3 years, 6 months ago 0

Definitely.

posted by dotnetchris(157) 3 years, 6 months ago 0

Kicked for absolutely being a must have.

posted by Egon(0) 3 years, 6 months ago 0

The debate has been largely philosophical so far. It would be nice to see some verifiable statistics to actually debate from a total cost efficiency perspective.

posted by cwbrandsma(1711) 3 years, 6 months ago 0

@Egon: and how would you go about creating said statistics?

posted by damo(0) 3 years, 6 months ago 0

Well if you are doing any sort of testing on your components you have to layer it. If wish to test your business logic properly you have to do it in isolation and it has to be repeatable. That means being able to swap out the database dependency with a mocked version.

If this guy is the MVP architect he claims he is, he would know this already.

Most Active Users

What's this?