Re: Data Layer architecture
- From: laimis <simulai@xxxxxxx>
- Date: Sat, 23 Jul 2005 17:06:34 -0500
Before you introduce extra layers of complexity, read this:
http://grumpyoldprogrammer.myblogsite.com/blog/_archives/2005/5/13/851175.html
Looks like everyone (including me) has to learn that the hard way though. :)
Well I think what this article and many other books, posts about software design, all underline one key software design rule: consider tradeoffs of your decisions.
And maybe to clarify, I am not thinking for every business layer class to have a corresponding data layer class and other crazy stuff. Not at all :) I just want that procedure or sql call out of my business objects. It is ugly and adds of bunchy of ugle sql code or procedures mixed up with business logic implemented in C#.
.
- Follow-Ups:
- Re: Data Layer architecture
- From: Nick Malik [Microsoft]
- Re: Data Layer architecture
- References:
- Data Layer architecture
- From: laimis
- Re: Data Layer architecture
- From: Nick Malik [Microsoft]
- Re: Data Layer architecture
- From: laimis
- Re: Data Layer architecture
- From: Wessel Troost
- Data Layer architecture
- Prev by Date: RE: Converting image to byte array
- Next by Date: RE: RichTextbox scroll to a line
- Previous by thread: Re: Data Layer architecture
- Next by thread: Re: Data Layer architecture
- Index(es):
Relevant Pages
|