Click here to Skip to main content
15,920,217 members
Home / Discussions / Design and Architecture
   

Design and Architecture

 
GeneralRe: Documenting Design Pin
K. Shaffer17-Jan-09 6:53
K. Shaffer17-Jan-09 6:53 
GeneralRe: Documenting Design Pin
Karthik Jegadeesan19-Jan-09 21:44
professionalKarthik Jegadeesan19-Jan-09 21:44 
GeneralRe: Documenting Design Pin
K. Shaffer22-Jan-09 12:50
K. Shaffer22-Jan-09 12:50 
GeneralRe: Documenting Design Pin
K. Shaffer22-Jan-09 13:00
K. Shaffer22-Jan-09 13:00 
QuestionDatabase Queries Pin
CodingYoshi6-Jan-09 17:20
CodingYoshi6-Jan-09 17:20 
AnswerRe: Database Queries Pin
Wendelius7-Jan-09 2:29
mentorWendelius7-Jan-09 2:29 
GeneralRe: Database Queries Pin
CodingYoshi7-Jan-09 8:49
CodingYoshi7-Jan-09 8:49 
GeneralRe: Database Queries Pin
Wendelius7-Jan-09 9:16
mentorWendelius7-Jan-09 9:16 
I wouldn't think that creating the library is a waste of time at all. One thing that's obvious benefit is that you get reusable code. Also considering the application maintenance you would have a single point to maintain and the benefits in performance, caching, services (methods etc), structural changes in data etc. would be usable for all. For example if later few more columns are needed by many application, simply adding them both to the procedure and to the class once would do the trick without rewriting several DAL's.

One thing I'm thinking of is that why you would take only few of the columns instead of all. If the application needs only few, you can strip the unnecessary columns away when the application requests for data or the application can do it if necessary. To go a bit further you could get some data around the customer (like number of orders or whatever) and if the app requests it you either fetch it or return if it's cached.

As said this is just an opinion but I'm used to the idea that only single DAL exists against one database. In my experience, it makes things a whole lot easier when you have to change something. Of course this DAL is cumulative so that when new tables or applications are created, the DAL grows but still it's "centralized". Although the development environment in my cases may be very different from yours.

The need to optimize rises from a bad design.My articles[^]

GeneralRe: Database Queries Pin
Jon Rista7-Jan-09 12:20
Jon Rista7-Jan-09 12:20 
GeneralRe: Database Queries Pin
Wendelius8-Jan-09 2:47
mentorWendelius8-Jan-09 2:47 
GeneralRe: Database Queries [modified] Pin
Jon Rista8-Jan-09 4:55
Jon Rista8-Jan-09 4:55 
GeneralRe: Database Queries Pin
Wendelius8-Jan-09 5:25
mentorWendelius8-Jan-09 5:25 
GeneralRe: Database Queries Pin
Jon Rista8-Jan-09 10:56
Jon Rista8-Jan-09 10:56 
GeneralRe: Database Queries Pin
Mark Churchill7-Jan-09 13:53
Mark Churchill7-Jan-09 13:53 
QuestionSoftware development Pin
systemexpertise1-Jan-09 18:26
systemexpertise1-Jan-09 18:26 
AnswerRe: Software development Pin
Cosmic Egg10-Jan-09 3:29
Cosmic Egg10-Jan-09 3:29 
QuestionStylesheet in VS2008 Pin
sarang_k30-Dec-08 19:01
sarang_k30-Dec-08 19:01 
AnswerRe: Stylesheet in VS2008 Pin
CodingYoshi4-Jan-09 15:45
CodingYoshi4-Jan-09 15:45 
QuestionException Hierarchy Pin
CodingYoshi29-Dec-08 11:27
CodingYoshi29-Dec-08 11:27 
GeneralRe: Exception Hierarchy Pin
Luc Pattyn29-Dec-08 15:12
sitebuilderLuc Pattyn29-Dec-08 15:12 
GeneralRe: Exception Hierarchy Pin
CodingYoshi30-Dec-08 3:18
CodingYoshi30-Dec-08 3:18 
AnswerRe: Exception Hierarchy Pin
Jon Rista6-Jan-09 8:48
Jon Rista6-Jan-09 8:48 
GeneralRe: Exception Hierarchy Pin
Leftyfarrell6-Jan-09 13:29
Leftyfarrell6-Jan-09 13:29 
GeneralRe: Exception Hierarchy Pin
Jon Rista6-Jan-09 17:31
Jon Rista6-Jan-09 17:31 
GeneralRe: Exception Hierarchy Pin
Curtis Schlak.25-Feb-09 9:02
Curtis Schlak.25-Feb-09 9:02 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.